_ registry / mcp streamable-http · checked 4h ago

offline-protocol

https://mcp.offlineprotocol.com

Registry code: 0db2ab2d7a4c9498

api record

Read-only access to the public Offline Protocol developer registry: SDK packages, product workflows, integration guides (skills), starter templates and a planner. No account is needed and nothing is written or changed. Results describe how to build an app; the server does not discover, connect to or control devices. Creating or editing project files is not available here; it needs the local Offline Protocol CLI (`offline mcp serve`).

endpoint
https://mcp.offlineprotocol.com/public/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is offline-protocol live?
Yes — it answered the hub's last check (checked 4h ago). It answered 99% of checks over the last 30 days.
Is offline-protocol free to use?
Not measured yet.
What tools does offline-protocol have?
15 tools: get_package, search_workflows, search_examples, get_workflow, list_skills, preview_scaffold, search_skills, get_skill, ….
Is offline-protocol safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.2%

90 days 99.1%· all time 99.1%

latency
408ms

last good check

priced tools
0

of 15 tools

_ answered our checks, 90 days 228 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
developer tools
used for
  • search sdk packages for offline apps
  • plan an app architecture
  • resolve packages for a platform
  • read an integration guide
  • preview a starter scaffold
takes → gives
text → data, text
tools
15 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 15 tools
15 never probed 0 of 15 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_package reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 128,
      "description": "Package name, e.g. @offline-protocol/mesh-sdk"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • search_workflows reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 200,
      "description": "Search keywords"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • search_examples reads unknown never probed

    Search Offline Protocol reference example apps and integrations by keyword.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 200,
      "description": "Search keywords"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • get_workflow reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 128,
      "description": "Workflow name, e.g. local-handoff, backend-delivery or nearby-service"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • list_skills reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • preview_scaffold reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 128,
      "description": "Project name / directory slug"
    },
    "prompt": {
      "type": "string",
      "maxLength": 2000,
      "description": "Natural-language app idea (uses the planner)"
    },
    "platform": {
      "enum": [
        "react-native",
        "nextjs",
        "react-vite",
        "web",
        "rust"
      ],
      "type": "string",
      "description": "Required when a multi-platform workflow is named without a template"
    },
    "template": {
      "type": "string",
      "maxLength": 128,
      "description": "Template name, e.g. react-native-social"
    },
    "workflow": {
      "type": "string",
      "maxLength": 128,
      "description": "Workflow name, e.g. local-handoff, backend-delivery or nearby-service"
    },
    "enableMesh": {
      "type": "boolean",
      "description": "Enable mesh SDK for React Native templates (default: true for mesh workflows / mesh templates)"
    },
    "enableOfflineId": {
      "type": "boolean",
      "description": "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 to react-native-social when true."
    }
  },
  "additionalProperties": false
}
    arguments 48 lines
  • search_skills reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 200,
      "description": "Search keywords"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • get_skill reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 128,
      "description": "Skill name, e.g. mesh-networking, identity, groups"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • resolve_packages reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "platform"
  ],
  "properties": {
    "packages": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 128
      },
      "maxItems": 25,
      "description": "Explicit package names to resolve"
    },
    "platform": {
      "enum": [
        "react-native",
        "nextjs",
        "react-vite",
        "web",
        "rust"
      ],
      "type": "string",
      "description": "Target platform"
    },
    "workflow": {
      "type": "string",
      "maxLength": 128,
      "description": "Alternatively, a workflow name to resolve"
    }
  },
  "additionalProperties": false
}
    arguments 34 lines
  • list_packages reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • search_packages reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 200,
      "description": "Search keywords"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • search_capabilities reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 200,
      "description": "Search keywords"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • list_workflows reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_template reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 128,
      "description": "Template name, e.g. react-native-mesh-app"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • generate_architecture reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "prompt"
  ],
  "properties": {
    "prompt": {
      "type": "string",
      "maxLength": 2000,
      "description": "What you want to build, e.g. 'Hand over equipment between field engineers and reconcile with our backend'"
    },
    "platform": {
      "enum": [
        "react-native",
        "nextjs",
        "react-vite",
        "web",
        "rust"
      ],
      "type": "string",
      "description": "Optional platform override; inferred from the prompt otherwise"
    }
  },
  "additionalProperties": false
}
    arguments 25 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 0db2ab2d7a4c9498.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/0db2ab2d7a4c9498/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/0db2ab2d7a4c9498/badge.svg)](https://brick.blue/agent/0db2ab2d7a4c9498?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.