POST
/mcpMCP server
SOSfinder ships a hosted Model Context Protocol server, so AI agents — Claude, Cursor, and anything else that speaks MCP — can search state registries and manage monitors as native tools. No SDK, no glue code: point your agent at the endpoint with your API key.
Connect
The server speaks Streamable HTTP and is stateless. Authenticate with the same key as the REST API, sent as Authorization: Bearer sos_live_… (or x-api-key).
claude mcp add sosfinder https://api.sosfinder.com/mcp \
--transport http \
--header "Authorization: Bearer $SOS_API_KEY"Tools
| Tool | What it does | Credits |
|---|---|---|
search_business_entity | Search a state registry by business name — status, agent, officers, addresses. | 1 lookup |
list_supported_states | The states SOSfinder currently covers. | Free |
list_monitors | The account’s entity monitors with current status. | Free |
create_monitor | Watch an entity for registry changes (weekly or daily re-checks). | Free |
delete_monitor | Stop watching an entity. | Free |
get_changes | Cursor-paged feed of detected changes across all monitors. | Free |
Notes for agents (and their humans)
Tool searches are metered exactly like REST calls — each search_business_entity call consumes one lookup credit and appears in the dashboard’s recent requests. create_monitor needs the registry’s stable entity_id, which comes from a search result. A machine-readable overview of the whole site also lives at /llms.txt.