Offline Protocol (hosted) MCP server
online · 100% uptimeby offlineprotocol.com·
com.offlineprotocol/hosted·v0.2.9Offline Protocol packages, workflows and integration guides over HTTPS. Read-only.
B73/100grade B
Safety scan
B73/100
not scanned yet
Adoption
New
Little public usage data yet
Reviews
Write oneNobody has reviewed Offline Protocol (hosted) yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Offline Protocol (hosted) tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Offline Protocol (hosted) compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 73/100
- higher than 39% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 259 ms
- faster than 54% of 30,031 servers
Release history: 4 versions in the registry since 2026-10-01, latest 2026-10-27, typically one every 5 days.
Install Offline Protocol (hosted) in Claude Code, Cursor or VS Code
claude mcp add --transport http hosted https://mcp.offlineprotocol.com/mcp
Offline Protocol (hosted): common questions
- Is Offline Protocol (hosted) MCP server safe?
- Mostly: it is graded B (73/100). Read the Offline Protocol (hosted) safety report
- How do I install Offline Protocol (hosted)?
- It runs remotely at mcp.offlineprotocol.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Offline Protocol (hosted) need an API key?
- Yes. The registry entry asks for
Authorization. - Is Offline Protocol (hosted) maintained?
- The latest release is v0.2.9.
- Is Offline Protocol (hosted) up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Offline Protocol (hosted) compare with other MCP servers?
- safety score 73/100 (higher than 39% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 259 ms (faster than 54% of 30,031 servers). Full comparison.