Developer · Remote MCP server
Costory FinOps MCP
FinOps MCP: query allocated, correlated cloud and AI cost across AWS, GCP, Azure and Snowflake.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.costory/finops- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-08-13
- Updated
- 2026-08-13
- Publisher
- io.costory
- Namespace
- Namespace verified by the MCP Registry via the domain costory.io · how
- Listed under
- Snowflake MCP servers, AWS MCP servers, Azure MCP servers, Google Cloud MCP servers
- Website
- docs.costory.io/features/mcp
- Repository
- github.com/costory-io/costory-finops-mcp-skills
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://app-api.costory.io/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Costory FinOps MCP
Costory FinOps MCP is a remote MCP server: there is nothing to install. Its endpoint is https://app-api.costory.io/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Cortex RMCPSelf-hosted homelab log intelligence over MCP, CLI, and REST with SQLite/FTS. | Local · stdio |
| Cortex RMCPRust MCP server for homelab logs, syslog, Docker logs, FTS search, and AI transcript correlation. | Local · stdio |
| CosmicManage Cosmic CMS content, media, object types, and AI generation from any MCP client. | Remote & Local · HTTP, stdio |
| Cosmos MCPPersonal knowledge graph every MCP client reads from and writes to. Portable across agents. | Local · stdio |
| CostPilotHosted MCP server for AWS cloud spend: service breakdowns, anomalies, savings and forecasts. | Remote · HTTPLive check: ✗ no handshake |
| COTAL actions (cotal.ai)Cotal.ai actions: product overview, site search, build log, feedback, Cloud waitlist, updates, calls. | Remote · HTTPLive check: ✓ handshake |
| Council AiMulti-LLM council: 25+ frontier models in parallel, consensus scoring, verdict-first code review. | Remote · HTTPLive check: ✓ handshake |
| Covalent BondPeer-to-peer, end-to-end-encrypted collaboration channel for AI coding agents over MCP. | Local · stdio |