Synapse Network MCP Server for paid API calls

by synapsenetworkai Your server? Claim it

not responding

Synapse Network MCP Server for paid API calls is listed as active in the registry but did not answer our last check. 31 installs a week from npm. Last commit 21 Jun 2026.

Synapse Network MCP paid API calls via discover_services; not Synapse.org/Sage Bionetworks Synapse.

Installs per day peak 16 · avg 6 · +25% w/w

a month agotoday

Uptime history 51 days of history · worst day 0%

51 days agonow

0.0%

Uptime 24h

0 of 92 checks

—

Tools

hidden behind auth

308 ms

Response time

average over 24h

Installs / week

npm and PyPI

Synapse Network MCP Server for paid API calls does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add synapse-network-mcp-server --transport http https://mcp.synapse-network.ai/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "synapse-network-mcp-server": {
      "url": "https://mcp.synapse-network.ai/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.synapse-network-mcp-server]
url = "https://mcp.synapse-network.ai/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "synapse-network-mcp-server": {
      "url": "https://mcp.synapse-network.ai/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "synapse-network-mcp-server": {
      "url": "https://mcp.synapse-network.ai/mcp"
    }
  }
}

This one needs environment variables set before it will start: SYNAPSE_AGENT_KEY (SynapseNetwork Agent Key beginning with agt_. Used as the Gateway X-Credential header.), SYNAPSE_ENV (Gateway environment preset: prod or staging. Use prod for production workflows; staging is for preview and E2E validation.), SYNAPSE_GATEWAY_URL (Optional custom Gateway base URL. Overrides SYNAPSE_ENV.). The author declared them in the registry entry; get the values from the project itself.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.synapse-network.ai/mcp	streamable-http	answering	308 ms	2 min ago

Alternatives to Synapse Network MCP Server for paid API calls

same job, measured the same way

Junos MCP

by shigechika

MCP server for Juniper Networks device operations via junos-ops

322 installs/wk local only

Domotz

by wyre-ai

MCP server for Domotz network monitoring — agents, devices, alerts, and network discovery.

local only

Domotz

by wyre-technology

MCP server for Domotz network monitoring — agents, devices, alerts, and network discovery.

local only

Satring MCP

by toadlybroodle

Discover and compare L402 + x402 paid API services from satring.com

39 installs/wk local only

Agenium MCP Server

by chorghemaruti64-creator

Bridge MCP servers to the AGENIUM agent:// network via DNS discovery

73 installs/wk local only

Agentictrade

by miranttie

AI service marketplace — agents discover, call, and pay for API services automatically.

5 tools answering

Scan MCP

by jacksenechal

MCP server for scanner discovery and batch capture via SANE

47 installs/wk local only

Agentstorefront

by lmaniraruta

MCP for AgentStorefront — discover, price, and subscribe to paid agent services.

28 installs/wk local only

Synapse Network MCP Server for paid API calls — questions

Answers built from our own checks of this server.

Is Synapse Network MCP Server for paid API calls working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 308 ms. The bar chart above shows every period we have measured.

The registry lists Synapse Network MCP Server for paid API calls as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Synapse Network MCP Server for paid API calls?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Synapse Network MCP Server for paid API calls need an API key?

No. Synapse Network MCP Server for paid API calls completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.

How many people use Synapse Network MCP Server for paid API calls?

The npm package @synapse-network-ai/mcp-server was installed 31 times in the last week. Week over week that is +25%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is Synapse Network MCP Server for paid API calls open source?

Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.