MCP | Chadwin

Connect and sign in

Add a remote MCP server in a client that supports MCP 2026-07-28, 2025-11-25, or 2025-06-18 over stateless Streamable HTTP with OAuth 2.1. Use this server URL:

https://mcp.chadwin.co/mcp

When the client opens Chadwin in your browser, sign in with your email, review the requested data:read access, and approve it. The client then stores its own OAuth credentials and tokens. Do not paste a Chadwin API key into the client.

Chadwin checks the OAuth token on every request and applies your current plan, dataset access, rate limit, and billing-period quota to each tool call.

Example requests

After the connection succeeds, ask the client for a bounded lookup such as:

Find IBM and return its current company record.
Get Apple's annual report for fiscal year 2025.
List open-market purchases filed since 2026-08-01 for AAPL.
Search for institutional managers named Berkshire.
Show the latest Form 13F report periods for manager 028-00001.

Use a ticker for a listed company, an SEC accession number for a filing, a CIK for an SEC filer, and a Form 13F file number for an institutional manager. Tool descriptions show the required format for each value.

Capabilities

The server provides bounded, read-only access to company discovery, company reports, insider ownership and proposed sales, institutional holdings, and event feeds. Your MCP client discovers the current tool names, descriptions, and input schemas from the server.

Each list operation returns one finite API page, and no operation writes Chadwin or SEC data.

For the source datasets and exact HTTP response fields, use the API reference. MCP results keep those JSON field names.

Pagination

A paged result may include next_cursor. To continue, call the same tool again with that value as cursor and keep the same filters. Treat the cursor as an opaque value and do not parse or edit it.

Feed tools return the latest matching events when cursor is absent and continue from the supplied cursor when it is present. The server does not fetch later pages in the background.

Auth and errors

An HTTP 401 means the access token is missing, expired, revoked, or invalid; sign in again through the client
An HTTP 403 before a tool call means the token lacks data:read
A schema or JSON-RPC error means the request shape or value is invalid; correct the named argument
A tool error returns a safe Chadwin error code and status, such as an entitlement 403 or quota 429, without internal headers or credentials
A temporary authorization, API, or runtime failure can be retried after a short delay

Compatibility

The hosted server supports MCP 2026-07-28, 2025-11-25, and 2025-06-18. It does not create an MCP session or session ID. Current-protocol calls use one JSON response per message; the two 2025 revisions use stateless Streamable HTTP compatibility responses.

The first release has no local stdio package, prompts, resources, subscriptions, write tools, filing HTML, hidden pagination, or start-from-now feed mode. A client must support the remote HTTP and OAuth flow described above.