_ registry / mcp + a2a http-sse · checked 37m ago

capability-host-protocol

https://capabilityhostprotocol.com

Registry code: 83fd7b1a8935ec77

api record

Learn and adopt the Capability Host Protocol — the agentic web's open evidence layer.

from a public catalogue that lists it, not from the operator

endpoint
https://www.capabilityhostprotocol.com/api/mcp
door code
4f61777be94d9643
protocol
http-sse ·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 capability-host-protocol live?
Yes — it answered the hub's last check (checked 37m ago). It answered 100% of checks over the last 30 days.
Is capability-host-protocol free to use?
Yes — the hub reached it with no key and no payment.
What tools does capability-host-protocol have?
9 tools: define, how_to_adopt, get_capability, faq, search, explain, list_adapters, get_example, ….
Is capability-host-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.6%

90 days 99.4%· all time 99.8%

latency
421ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1398 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
knowledge & reference documentation & docs search
used for
  • learn how a protocol works
  • look up protocol terms
  • find adapters and capabilities
  • get adoption steps and examples
takes → gives
text → text, data
tools
9 reads
note
documentation mirror
_ 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 9 tools
3 open 6 never probed 3 of 9 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.

  • list_adapters reads open 10h ago

    Browse the open adapter ecosystem, optionally by category.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "category": {
      "type": "string"
    }
  }
}
    arguments 9 lines
  • get_example reads open 10h ago

    Get a runnable example. Pass a name, or omit to list examples. Names: hooks-install, inspect-session, minimal, agentic, rag, safety, persistence, evidence-output.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "name": {
      "type": "string"
    }
  }
}
    arguments 9 lines
  • list_capabilities reads open 37m ago

    List the capabilities the open CHP adapter ecosystem declares, optionally by category.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "category": {
      "type": "string"
    }
  }
}
    arguments 9 lines
  • define reads unknown never probed

    Define a CHP primitive. Pass a term, or omit to list the glossary.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "term": {
      "type": "string"
    }
  }
}
    arguments 9 lines
  • how_to_adopt reads unknown never probed

    Get the steps to start using CHP (begin with agents).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_capability reads unknown 10h ago

    Resolve a capability id to its descriptor.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string"
    }
  }
}
    arguments 12 lines
  • faq reads unknown never probed

    Common questions about CHP. Pass a query to filter, or omit for all.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "query": {
      "type": "string"
    }
  }
}
    arguments 9 lines
  • search reads unknown 37m ago

    Search CHP concepts, glossary, FAQs, and the capability catalog.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string"
    }
  }
}
    arguments 12 lines
  • explain reads unknown never probed

    Learn what CHP is and how it works. Pass a topic, or omit to list topics. Topics: what-is-chp, evidence-model, why-a-protocol, governance, agentic-web, evidence-vs-telemetry, chp-vs-mcp, conformance.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "topic": {
      "type": "string"
    }
  }
}
    arguments 9 lines
_ try it over mcp 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 83fd7b1a8935ec77.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/83fd7b1a8935ec77/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/83fd7b1a8935ec77/badge.svg)](https://brick.blue/agent/83fd7b1a8935ec77?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 knowoff the mcp door
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.