com.synapseorch/synapseorch
SynapseOrch
Is the SynapseOrch MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-13.
Build and run AI agent workflows: start runs, answer what they ask, search knowledge, edit agents.
needs auth probed 2026-11-14 · unchanged since 2026-11-13 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"detail": "A Synapse API key (Authorization: Bearer sk-syn-\u2026) or an OAuth access token for this server i- Endpoint
- https://api.synapseorch.com/api/v1/mcp (streamable-http)
- Host
- api.synapseorch.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://api.synapseorch.com/api/v1/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server api.synapseorch.com, PKCE S256, grants authorization_code, refresh_token.
Scopes read run build.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/synapseorch-ai/synapse-ai
- Website
- https://synapseorch.com
- Registry
- active, updated 2026-11-13 · registry entry
Compare this server with others.
More servers
Servers that mention knowledge or workflows.
- inference.sh ac.inference.sh/mcp · needs auth
- ac.tandem/docs-mcp · alive
- Knowledge Base ai.b77/knowledge-base · needs auth
- brainattic ai.brainattic/knowledge-base · needs auth
- China Marketing AI Intelligence MCP ai.chinamarketing/intelligence · needs auth
- Buron ai.buron/buron · paid (402)
- ColdState — Deterministic Knowledge Infrastructure ai.coldstate/knowledge · alive
- DeepDNA ai.deepdna/knowledge · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.