MCP (coming soon)
The planned hosted Model Context Protocol server for Clous at mcp.clous.ai, so AI agents can call SEC filing tools directly.
MCP
Coming soon. The hosted MCP server is on the roadmap and is not live yet. The REST API on this page's siblings is live today — start there.
Clous is built to be MCP-native. Alongside the REST API, Clous is bringing a hosted Model Context Protocol server so AI agents can call SEC filing tools directly, without writing HTTP glue.
Planned hosted endpoint
- MCP server:
https://mcp.clous.ai - Auth: the same Bearer key as REST —
Authorization: Bearer clous_live_... - Envelope: tools return the same
{ data, page, as_of, source, query_echo, warnings }envelope as the REST API, so what you learn here transfers directly.
Why MCP
- No glue code. An MCP-capable agent discovers Clous tools and their typed parameters automatically.
- Consistent contract. Tool results use the same envelope and the same error codes as REST.
- Source-linked. Every record still carries provenance and freshness, so an agent can cite the underlying filing.
Example agent prompts (planned)
Once the MCP server is live, an agent connected to mcp.clous.ai will be able to act
on prompts like:
- "List New York investment advisers with over $1B in regulatory AUM and tell me which report private funds."
- "Resolve CRD 105958 to a canonical entity and summarize its Form ADV profile."
- "Find advisers with disciplinary history in California and link each to its source filing."
In the meantime
Use the live REST endpoints — see the Quickstart and the
Advisers API Reference. The machine-readable
llms.txt index lets agents navigate the API today.