mcpbeat Sign in

SoloFire MCP Server

answering

SoloFire is answering right now. Last checked moments ago.

Med device and life science sales enablement: search content, share tracked Spaces, see engagement.

Uptime history 53 days of history · worst day 95%
53 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
693 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

SoloFire missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add spark --transport http https://developer.solofire.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://developer.solofire.com/mcp
~/.codex/config.toml
[mcp_servers.spark]
url = "https://developer.solofire.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "spark": {
      "url": "https://developer.solofire.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "spark": {
      "type": "http",
      "url": "https://developer.solofire.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://developer.solofire.com/mcp streamable-http sign-in 480 ms 0 min ago

Alternatives to SoloFire

same job, measured the same way
Letter AI
by tractatus-ai

Search and act on Letter AI sales enablement content, deals, and call recordings.

answering
Contextful
by inferensys

Efficient context management: code search, evidence packs, and memory for coding agents.

38 installs/wk local only
EUDAMED MCP
by t4dhg

Search public EUDAMED devices, verify actors and build traceable evidence checklists.

81 installs/wk local only
MediaPact
by mediapact

Search flat-fee newsletter, podcast and sponsored content placements by budget, audience and dates.

answering
OpenComment AI
by 02inf

Research saved LinkedIn contacts, review monitored activity, and prepare engagement campaigns.

4 tools answering
Lore Context
by lore-context

Governed AI-agent memory, Evidence Ledger traces, evals, and portable context tools.

25 installs/wk local only
Canada Medical Device Licences MCP
by donniertf-hub

Is this medical device licensed in Canada? Search Health Canada MDALL and verify licences.

4 tools answering
Exa Search
by pollinations

Search the live web and fetch clean content from source pages.

answering

SoloFire — questions

Answers built from our own checks of this server.

Why is there no tool list for SoloFire?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is SoloFire working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 693 ms. The bar chart above shows every period we have measured.
How do I connect SoloFire?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to SoloFire?
No API key is involved. SoloFire answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is SoloFire?
It answers our handshake in 693 ms on average, which is faster than 14% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.