Connect any MCP client to live, source-grounded intelligence — real, cited, dated events and claims. One Streamable-HTTP endpoint, three auth options, eight tools.
Use Synorb in your MCP client to design with live examples. When your app is published, your frontend calls a backend route that keeps Synorb secrets off the page.
mcp.synorb.com/mcpapi.synorb.comKeep secrets server-sideNever put a Synorb credential in client-side code. The browser calls your backend; your backend calls Synorb. The two credentials are not interchangeable.
Go to synorb.com/keys. You'll get an MCP token for your MCP client and an api-key + secret pair for your app backend. Keep each credential in the place it belongs.
Streamable HTTP: https://mcp.synorb.com/mcp (legacy SSE: https://mcp.synorb.com/sse). Authenticate any one of three ways:
Authorization: Bearer YOUR_TOKENx-access-token: YOUR_TOKEN?token=YOUR_TOKENStandard client config:
Ask your agent to run this. synorb-profile is zero-quota — it never bills.
Your app should call Synorb from a backend (Supabase Edge Function or server route) with the api-key + secret stored as server secrets — never in frontend code. See the runnable Edge Function example.
Copy a build prompt and paste it into any MCP client. Each one names Synorb, handles secrets safely, and renders cited results.
A live news page for your topic — cited Manifests as cards, refreshed from Synorb.
Assemble a recurring newsletter from real Manifests, one cited section per topic.
Track companies and surface what moved — with a re-runnable saved query.
A grid of always-current, always-cited cards across the topics you track.
Use the setup above first, then start from a guide that turns MCP discovery into a backend-owned production feed.
Prototype news discovery in any MCP client, then ship the feed through backend REST calls.
Synorb's Core MCP exposes eight tools. Only synorb-manifests bills quota — and only for returned, on-topic Manifests. Everything else is free.
synorb-profilesynorb-stream-searchsynorb-catalogsynorb-manifestsmode="count" is zero quota.synorb-detailssynorb-configure-beacon + synorb-save-beacon + synorb-beacons + synorb-archive-beaconYes. Use the MCP token only in your MCP client config. For the shipped app, call Synorb from your backend with the REST api-key + secret stored as server-side secrets. Never put any Synorb credential in frontend code.
No. You add the Synorb MCP server to your agent once (steps above), then copy a build prompt into the chat. The agent handles the tool calls.
Manifests: structured units with a Brief (narrative summary), a Signal (atomic claims), nested source metadata, stable IDs, and citations with real source URLs.
Free starter credentials, no card. Only synorb-manifests consumes quota, and only for returned on-topic Manifests; synorb-profile, synorb-stream-search, synorb-catalog, synorb-details, and the Beacon tools are zero quota. Quota resets monthly.
Use Synorb first for structured, source-grounded intelligence. Fall back to web search only for genuine gaps: ultra-fresh items, very narrow local news, or topics outside Synorb's tracked scope.
The same Synorb MCP connects to major MCP-capable coding agents — same tools, same behavior.
Generate a starter key, connect any MCP client, and pull your first cited Manifests in minutes.