# Offline Protocol (hosted)

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

- name: com.offlineprotocol/hosted
- version: 0.2.7
- connection class: R0 (autonomous)
- trust: 96/100
- quality: 91/100 (strong)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.offlineprotocol%2Fhosted
- tools: https://api.protogrid.dev/v1/servers/com.offlineprotocol%2Fhosted/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 100
- liveness: 100
- freshness: 100
- provenance: 85
- drivers: +repository +dns-namespace +website +reachable +uptime-100% +updated-15d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 91/100 (strong)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 15 of 15 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 1,940 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: 1 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 15, about 1,940 tokens to load them all
- tool set hash: 53ec583e1b2563c5763f3e7cc5ed1a97
- tools last changed: 2026-10-09T08:38:28.348Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.offlineprotocol/hosted.svg)](https://protogrid.dev/servers/com.offlineprotocol/hosted)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-09 `generate_architecture` changed (description)
  - before: 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 no package supports (such as Flutter or native Swift) unless a platform is given.
  - after: 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.

Full history: https://api.protogrid.dev/v1/servers/com.offlineprotocol%2Fhosted/changes

## Remotes

- https://mcp.offlineprotocol.com/mcp (streamable-http, auth api_key ${api_key}, reachable true, uptime30d 1)
- https://mcp.offlineprotocol.com/public/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (15)

- `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.
- `get_package`: Get one Offline Protocol package's registry entry: capabilities, peer dependencies, platform requirements, integration notes and examples.
- `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.
- `get_template`: Get an Offline Protocol starter template's metadata: variables, post-generation steps, notes and file list. Creates no files.
- `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).
- `list_packages`: List every Offline Protocol SDK package in the public registry with its version, supported platforms, capabilities and license.
- `list_skills`: List every Offline Protocol integration guide (skill) with the situations it covers.
- `list_workflows`: List every Offline Protocol product workflow with its capabilities and supported platforms.
- `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.
- `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.
- `search_capabilities`: Search Offline Protocol capabilities, such as peer discovery or encrypted groups, and see which packages, workflows and guides provide each one.
- `search_examples`: Search Offline Protocol reference example apps and integrations by keyword.
- `search_packages`: Search Offline Protocol SDK packages by name, capability or description keywords. Returns ranked matches.
- `search_skills`: Search Offline Protocol integration guides (skills) by topic. Returns matching guide names.
- `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.