# Offline Protocol (hosted) (remote · mcp.offlineprotocol.com)

Offline Protocol packages, workflows and integration guides over HTTPS. Read-only.

- Trust score: 85/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.offlineprotocol.com`: 33/100, [markdown](https://verifymcp.io/servers/com-offlineprotocol-hosted/mcp.md), [page](https://verifymcp.io/servers/com-offlineprotocol-hosted/mcp)
- remote · `mcp.offlineprotocol.com`: 85/100 (this document), [markdown](https://verifymcp.io/servers/com-offlineprotocol-hosted/public-mcp.md), [page](https://verifymcp.io/servers/com-offlineprotocol-hosted/public-mcp)

## Channel facts

- Endpoint: `https://mcp.offlineprotocol.com/public/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-offlineprotocol-hosted 'https://mcp.offlineprotocol.com/public/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-offlineprotocol-hosted": {
      "url": "https://mcp.offlineprotocol.com/public/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-offlineprotocol-hosted": {
      "type": "http",
      "url": "https://mcp.offlineprotocol.com/public/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-offlineprotocol-hosted]
url = "https://mcp.offlineprotocol.com/public/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-offlineprotocol-hosted": {
      "type": "remote",
      "url": "https://mcp.offlineprotocol.com/public/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-offlineprotocol-hosted --url 'https://mcp.offlineprotocol.com/public/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-offlineprotocol-hosted:
    url: "https://mcp.offlineprotocol.com/public/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-offlineprotocol-hosted": {
      "Transport": "http",
      "Url": "https://mcp.offlineprotocol.com/public/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-offlineprotocol-hosted -t streamable-http -u 'https://mcp.offlineprotocol.com/public/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-offlineprotocol-hosted": {
      "type": "http",
      "url": "https://mcp.offlineprotocol.com/public/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 85, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] HSTS header: fail → unverified
- [security regression] Stability: pass → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-10-31 (score 85, 0)

- [security] Stability: 0.97 → pass

### 2026-10-29 (score 85, +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.

### 2026-10-27 (score 84, +1)

- [functional] New resource “Package: offline-protocol-web”
- [functional] New resource “Package: offline-protocol-ruby”
- [functional] Server version: 0.2.8 → 0.2.9

### 2026-10-25 (score 83, +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.

### 2026-10-23 (score 82, +1)

- [functional regression] 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

### 2026-10-21 (score 81, +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.

### 2026-10-19 (score 80, +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.

## MCP tools (15)

### `list_packages` (~29 tokens)

List packages

List every Offline Protocol SDK package in the public registry with its version, supported platforms, capabilities and license.

### `get_package` (~50 tokens)

Get package

Get one Offline Protocol package's registry entry: capabilities, peer dependencies, platform requirements, integration notes and examples.

Input parameters:

- `name` (string, required): Package name, e.g. @offline-protocol/mesh-sdk

### `search_packages` (~34 tokens)

Search packages

Search Offline Protocol SDK packages by name, capability or description keywords. Returns ranked matches.

Input parameters:

- `query` (string, required): Search keywords

### `search_capabilities` (~43 tokens)

Search capabilities

Search Offline Protocol capabilities, such as peer discovery or encrypted groups, and see which packages, workflows and guides provide each one.

Input parameters:

- `query` (string, required): Search keywords

### `search_workflows` (~50 tokens)

Search workflows

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.

Input parameters:

- `query` (string, required): Search keywords

### `search_examples` (~28 tokens)

Search examples

Search Offline Protocol reference example apps and integrations by keyword.

Input parameters:

- `query` (string, required): Search keywords

### `search_skills` (~34 tokens)

Search skills

Search Offline Protocol integration guides (skills) by topic. Returns matching guide names.

Input parameters:

- `query` (string, required): Search keywords

### `list_workflows` (~22 tokens)

List workflows

List every Offline Protocol product workflow with its capabilities and supported platforms.

### `get_workflow` (~62 tokens)

Get workflow

Get one Offline Protocol workflow in full: capabilities, packages per platform, starter templates and the reference architecture (screens, services, events and data models).

Input parameters:

- `name` (string, required): Workflow name, e.g. local-handoff, backend-delivery or nearby-service

### `list_skills` (~24 tokens)

List skills

List every Offline Protocol integration guide (skill) with the situations it covers.

### `get_skill` (~57 tokens)

Get skill

Read one Offline Protocol integration guide (skill): API usage, code samples and practices for one area, such as mesh networking, identity or groups.

Input parameters:

- `name` (string, required): Skill name, e.g. mesh-networking, identity, groups

### `resolve_packages` (~74 tokens)

Resolve packages

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.

Input parameters:

- `packages` (array): Explicit package names to resolve
- `platform` (string, required): Target platform
- `workflow` (string): Alternatively, a workflow name to resolve

### `get_template` (~50 tokens)

Get template

Get an Offline Protocol starter template's metadata: variables, post-generation steps, notes and file list. Creates no files.

Input parameters:

- `name` (string, required): Template name, e.g. react-native-mesh-app

### `generate_architecture` (~114 tokens)

Generate architecture

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.

Input parameters:

- `platform` (string): Optional platform override; inferred from the prompt otherwise
- `prompt` (string, required): What you want to build, e.g. 'Hand over equipment between field engineers and reconcile with our backend'

### `preview_scaffold` (~211 tokens)

Preview scaffold

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.

Input parameters:

- `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, required): 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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-offlineprotocol-hosted/public-mcp#diagnostics

## Score history

- 2026-11-05: 85
- 2026-11-04: 85
- 2026-11-03: 85
- 2026-11-02: 85
- 2026-11-01: 85
- 2026-10-31: 85
- 2026-10-30: 85
- 2026-10-29: 85
- 2026-10-28: 84
- 2026-10-27: 84
- 2026-10-26: 83
- 2026-10-25: 83
- 2026-10-24: 82
- 2026-10-23: 82
- 2026-10-22: 81
- 2026-10-21: 81
- 2026-10-20: 80
- 2026-10-19: 80
- 2026-10-18: 79
- 2026-10-17: 79
- 2026-10-16: 78
- 2026-10-15: 78
- 2026-10-14: 78
- 2026-10-13: 77
- 2026-10-12: 77
- 2026-10-10: 76
- 2026-10-07: 74
- 2026-10-05: 73
- 2026-10-04: 73
- 2026-10-03: 72

## Common questions

### 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.

## Links

- Remote endpoint: https://mcp.offlineprotocol.com/public/mcp
- Repository: https://github.com/Offline-Protocol/offline-protocol-agent-plugins
- Website: https://www.offlineprotocol.com/docs/tools/overview
- Changelog RSS feed: https://verifymcp.io/servers/com-offlineprotocol-hosted/public-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-offlineprotocol-hosted/public-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-offlineprotocol-hosted/public-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-offlineprotocol-hosted/public-mcp