Connect Synoptic MCP and inspect the actual SEC tools

Use the documented remote endpoint

The endpoint is https://mcp.api.synoptic.com/mcp, without a trailing slash. The official guide also provides an SSE endpoint for clients restricted to that transport; use Streamable HTTP where your client supports it.

A client’s configuration format is application-specific. The following Cursor configuration is reproduced from the documented structure. The remote endpoint was exercised directly in our probe; a Cursor user-interface session was not tested.

{
  "mcpServers": {
    "synoptic": {
      "url": "https://mcp.api.synoptic.com/mcp"
    }
  }
}

Documented Cursor configuration shape. Public discovery can work without sign-in; post tools require OAuth and account access.

Inspect these schema differences first

These argument names came from the live tools/list response saved on 2026-11-14. get_stream_posts and search_stream_posts use different names for the stream identifier. Copying a REST path or inventing a ticker argument will not substitute for the tool schema.

Do a public discovery check first

1. Call search with {"query":"SEC","limit":10}.
2. Inspect candidate titles and descriptions.
3. Call get_stream with {"id":"01JSPH2HZMMND30770DECW091Q"}.
4. Verify that this is the intended SEC stream and inspect API/access metadata.
5. If you need stored posts, complete OAuth and confirm stream entitlement.
6. Read the tool schema again before making the authenticated request.

Public steps 1–3 were actually exercised. Authenticated post reading and client UI configuration were not tested.

A successful connection does not establish data access

If the server lists tools but a post request returns an authentication error, that is an access boundary, not proof the stream contains no events. If authentication succeeds but a stream is inaccessible, confirm the account’s subscription and applicable restrictions.

Avoid changing follows or targets while diagnosing a read request. Use the smallest read-only test first and keep the stream ID, date window and returned error in the test record.