01 / OVERVIEW
A thin adapter to Tidelight’s hosted MCP.
The package source lives in public/components/mcp/server in the mother repository. It implements a local stdio server that forwards MCP tool discovery and calls to https://mcp.tidelight.app/mcp over the official Streamable HTTP transport.
It carries no research logic or provider access. The remote Tidelight service validates the project key and scopes, filters available tools, applies quotas, and returns the structured result. Use direct remote MCP with OAuth where your client supports it; use this bridge for local stdio-only integrations.
02 / QUICKSTART
Install the published bridge or build from source.
Install with the command shown above; these commands build and test the canonical source. The client config uses an absolute path to the built CLI.
cd public/components/mcp/server
npm ci
npm test
npm run build
export TIDELIGHT_API_KEY='YOUR_TIDELIGHT_PROJECT_KEY'
node ./dist/cli.jsKeep the project key in your MCP client’s protected environment. The bridge reads TIDELIGHT_API_KEY, never writes the credential into MCP tool results, and reports connection errors to stderr without including the key.
03 / AVAILABLE TOOLS
Upstream discovery follows key scopes.
tidelight_search_tokenized_equitiesmarket:read · Search supported Reality tokenized-equity spot instruments.tidelight_get_tokenized_equitymarket:read · Filter supported instruments by underlying US ticker.tidelight_start_company_researchresearch:run · Start an asynchronous company snapshot job.tidelight_get_research_jobresearch:run · Retrieve status and completed structured results.tidelight_cancel_research_jobresearch:run · Request cancellation of queued or running work.Tool responses are forwarded from the hosted service without local reinterpretation. Instrument data includes the Tidelight source context; research results do not expose private model reasoning.
04 / EXAMPLES
Connect a stdio-only client.
The client configuration above uses the canonical source build and keeps credentials in the client’s protected environment. After connection, the client discovers only the tools allowed by the project key’s current scopes. A package-level integration test exercises scoped discovery and a real protocol tool invocation against an in-memory upstream service.
For clients that support remote Streamable HTTP and OAuth, use the hosted endpoint directly; the local bridge is not required.
05 / COMPATIBILITY
Local and hosted transports.
The package source tests proxy behavior with the official TypeScript MCP SDK. That does not certify a named desktop or coding client’s complete setup and authorization behavior. Direct hosted connections can use OAuth when supported by the client.
06 / SECURITY & TRUST
Credentials and authority stay separated.
- API keys must be passed through the local process environment or a protected client secret store.
- Only HTTPS upstream endpoints are accepted, except loopback HTTP for local development tests.
- The proxy validates key shape locally; Tidelight validates the live key and its current scopes remotely.
- Connection errors are summarized without returning the upstream response body or credential.
- Market access, research permissions, provider availability, and quotas remain enforced by the hosted service.
This package is not a standalone replacement for mcp.tidelight.app and does not bypass server-side controls.
RELEASE / LIVE REGISTRY
Published release details
Version, installation, registry status, and archive details below are refreshed from the public registry.
Official Tidelight MCP stdio bridge
npm install @tidelight/mcp@0.1.1