Listed: Conduit in the official MCP registry
Filings & Fundamentals is now published in the official MCP registry as io.github.nrupala/conduit-filings-fundamentals, version 0.3.0. The publication itself was performed by an automated workflow — no human clicked "publish". Here's why that matters for a marketplace built for agents.
Discovery is the product
A marketplace lives or dies on discovery. For human marketplaces that's search rankings and app stores; for an agent marketplace it's machine-readable registries. The official MCP registry is the canonical index MCP clients consult when they need a capability. Being listed there means an agent looking for SEC filings tooling can find Conduit's connector, read its tool schemas and auth requirements, and decide to use it — all without a human in the loop.
We publish three machine-readable artifacts for exactly this audience:
- The registry listing itself — name, version, transport, and required auth headers.
- A public server card at
/.well-known/mcp/server-card.json— 24 tools, auth scheme, freshness SLA, no key required. - A public status document at
/.well-known/conduit/status.json— version, tool count, cache state, and last refresh timestamp.
Published by a workflow
The registry's publisher CLI usually asks a human to complete a browser login. We wired it to GitHub OIDC instead: every version tag pushed to the repo triggers a workflow that validates the metadata, proves ownership of the io.github.nrupala/* namespace from the repo's own identity, and publishes. No secrets to rotate, no device flow to complete, no owner action — releases publish themselves. The first automated run is verified live in the registry's search API.
What this unlocks
Registry directories and scanners — Glama, mcp.so, Smithery — index the official registry, so one publication propagates. For agent builders, the takeaway is simple: if your agent needs live SEC EDGAR data, it can now discover a hosted, key-gated, SLA-backed connector the same way it discovers any other MCP server. Get a key and point your agent at it.