Offline Protocol (hosted)
REMOTE · MCP.OFFLINEPROTOCOL.COM · 2 COMPONENTS
Offline Protocol packages, workflows and integration guides over HTTPS. Read-only.
Available components
Last scanned (11 hours ago)
Scores higher than 91% of remote servers
Unreachable for 2 days in a row. Last reached 3 Nov 2026.
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (3)
- HTTPS
- DNSSEC
- Transport
Checks we could not complete (8)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
- New resource “Package: offline-protocol-web” functional
- New resource “Package: offline-protocol-ruby” functional
- Server version: 0.2.8 → 0.2.9 functional
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
- Resource “Skill: Python, Rust, Swift and Android Packages” was removed ▼ functional
- New resource “Package: offline-protocol-flutter” functional
- New resource “Package: offline-protocol-c” functional
- New resource “Package: offline-protocol-java” functional
- New resource “Skill: Packages Beyond React Native” functional
- Server version: 0.2.7 → 0.2.8 functional
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.offlineprotocol.com/public/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.offlineprotocol.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| offlineprotocol.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.offlineprotocol.com/public/mcp | Unreachable | ||
| http (plaintext) | http://mcp.offlineprotocol.com/public/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
generate_architecture Generate architecture ~114
Turn an app idea into an Offline Protocol plan: matching workflow, platform, packages, starter template and architecture documents, returned as text. Returns an error, not a guess, when the idea needs a framework the planner has no starter for (such as Flutter or native Swift) unless a platform is given.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | – | Optional platform override; inferred from the prompt otherwise |
| prompt | string | yes | What you want to build, e.g. 'Hand over equipment between field engineers and reconcile with our backend' |
No output schema declared.
No examples provided.
get_package Get package ~50
Get one Offline Protocol package's registry entry: capabilities, peer dependencies, platform requirements, integration notes and examples.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Package name, e.g. @offline-protocol/mesh-sdk |
No output schema declared.
No examples provided.
get_skill Get skill ~57
Read one Offline Protocol integration guide (skill): API usage, code samples and practices for one area, such as mesh networking, identity or groups.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Skill name, e.g. mesh-networking, identity, groups |
No output schema declared.
No examples provided.
get_template Get template ~50
Get an Offline Protocol starter template's metadata: variables, post-generation steps, notes and file list. Creates no files.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Template name, e.g. react-native-mesh-app |
No output schema declared.
No examples provided.
get_workflow Get workflow ~62
Get one Offline Protocol workflow in full: capabilities, packages per platform, starter templates and the reference architecture (screens, services, events and data models).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Workflow name, e.g. local-handoff, backend-delivery or nearby-service |
No output schema declared.
No examples provided.
list_packages List packages ~29
List every Offline Protocol SDK package in the public registry with its version, supported platforms, capabilities and license.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_skills List skills ~24
List every Offline Protocol integration guide (skill) with the situations it covers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_workflows List workflows ~22
List every Offline Protocol product workflow with its capabilities and supported platforms.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
preview_scaffold Preview scaffold ~211
Preview what an Offline Protocol starter would contain for an app: workflow, template, packages and file list. A dry run that writes nothing; creating the project needs the local Offline Protocol CLI.
| Name | Type | Req | Description |
|---|---|---|---|
| enableMesh | boolean | – | Enable mesh SDK for React Native templates (default: true for mesh workflows / mesh templates) |
| enableOfflineId | boolean | – | Enable Offline ID (id-react-native) for React Native templates. Default: true for offline-social-network / offline-id-mesh-chat workflows and react-native-social; auto-switches react-native-mesh-app… |
| name | string | yes | Project name / directory slug |
| platform | string | – | Required when a multi-platform workflow is named without a template |
| prompt | string | – | Natural-language app idea (uses the planner) |
| template | string | – | Template name, e.g. react-native-social |
| workflow | string | – | Workflow name, e.g. local-handoff, backend-delivery or nearby-service |
No output schema declared.
No examples provided.
resolve_packages Resolve packages ~74
Resolve Offline Protocol packages, or a workflow, for one platform into an exact install list: versions, required and peer dependencies, install commands and license notes.
| Name | Type | Req | Description |
|---|---|---|---|
| packages | array | – | Explicit package names to resolve |
| platform | string | yes | Target platform |
| workflow | string | – | Alternatively, a workflow name to resolve |
No output schema declared.
No examples provided.
search_capabilities Search capabilities ~43
Search Offline Protocol capabilities, such as peer discovery or encrypted groups, and see which packages, workflows and guides provide each one.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search keywords |
No output schema declared.
No examples provided.
search_examples Search examples ~28
Search Offline Protocol reference example apps and integrations by keyword.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search keywords |
No output schema declared.
No examples provided.
search_packages Search packages ~34
Search Offline Protocol SDK packages by name, capability or description keywords. Returns ranked matches.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search keywords |
No output schema declared.
No examples provided.
search_skills Search skills ~34
Search Offline Protocol integration guides (skills) by topic. Returns matching guide names.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search keywords |
No output schema declared.
No examples provided.
search_workflows Search workflows ~50
Search Offline Protocol product workflows, such as local handoff, nearby chat, backend delivery or OfflineID sign-in, by keywords describing what you want to build.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search keywords |
No output schema declared.
No examples provided.
How do I install the Offline Protocol (hosted) MCP server?
Offline Protocol (hosted) is a hosted endpoint at https://mcp.offlineprotocol.com/public/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.offlineprotocol.com
claude mcp add --transport http com-offlineprotocol-hosted 'https://mcp.offlineprotocol.com/public/mcp'
What is the Offline Protocol (hosted) MCP server?
Offline Protocol (hosted) is an MCP server listed in the public MCP registry as com.offlineprotocol/hosted. Offline Protocol packages, workflows and integration guides over HTTPS. Read-only. This page covers its hosted endpoint (https://mcp.offlineprotocol.com/public/mcp).
Is the Offline Protocol (hosted) MCP server safe to use?
Offline Protocol (hosted) scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Offline Protocol (hosted) MCP server expose?
Offline Protocol (hosted) exposes 15 tools: list_packages, get_package, search_packages, search_capabilities, search_workflows, and 10 more. Their descriptions and schemas cost roughly 882 tokens of context every time the server is loaded.
Does the Offline Protocol (hosted) MCP server require authentication?
Its publisher declares no required credentials for Offline Protocol (hosted). We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Offline Protocol (hosted) MCP server still maintained?
Offline Protocol (hosted) is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Offline Protocol (hosted) MCP server?
VerifyMCP ran 3 checks on Offline Protocol (hosted), covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about Offline Protocol (hosted): TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.