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

keel

https://app.keelgrc.com

Registry code: 9ecca02b1a95c858

api record
endpoint
https://app.keelgrc.com/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 keel live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is keel free to use?
Yes — the hub reached it with no key and no payment.
What tools does keel have?
3 tools: requirement_get, crosswalk_lookup, frameworks_list.
Is keel 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
100%

90 days 100%· all time 100%

latency
1,522ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 3 checks · signed record
  • unknown → live
_ 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 3 tools
1 open 2 never probed 1 of 3 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.

  • frameworks_list open 1h ago

    List the compliance frameworks in Keel's open crosswalk dataset. Takes no arguments; needs no Keel account. Returns {"frameworks":[{"key","name","controls","url"}]}, where "controls" is how many canonical controls in Keel's library map to that framework. It is not the framework's own requirement count. Pass a "key" to crosswalk_lookup or requirement_get.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • requirement_get unknown 1h ago

    Start from one requirement and find the Keel controls mapped to it, with every other framework clause each control also satisfies. Needs no Keel account. "framework" takes a key from frameworks_list; "clause" is the requirement ref as the framework writes it (e.g. "CC6.1" for SOC 2, "A.8.5" for ISO 27001, "164.312(a)(1)" for HIPAA). Returns "controls" as [{"key","name","description","alsoSatisfies"}], where "alsoSatisfies" maps each other framework key to its clause refs. When the clause has no mapped control, "controls" is empty and "nearby" lists refs in the dataset that start the same way, widening to the parent ref when needed. No clause text is returned.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "framework",
        "clause"
      ],
      "properties": {
        "clause": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "Requirement ref, e.g. \"CC6.1\"."
        },
        "framework": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "Framework key, e.g. \"soc-2\"."
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
  • crosswalk_lookup unknown 1h ago

    Find the Keel controls that satisfy requirements in two compliance frameworks at once, so the work is done once and counts toward both. Needs no Keel account. "framework_a" and "framework_b" take a key from frameworks_list (e.g. "soc-2", "iso-27001"); a framework name also works. Returns "shared" (the number of shared controls), "controls" as [{"key","name","clausesA","clausesB"}] with the clause refs each control maps to on each side, "page" (the public crosswalk page for the pair) and "onYourProgram" (links to see the same mapping in a Keel workspace). Clause refs are written as Keel writes them; no clause text is returned. Use requirement_get to start from one clause instead.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "framework_a",
        "framework_b"
      ],
      "properties": {
        "framework_a": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "First framework key, e.g. \"soc-2\"."
        },
        "framework_b": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "Second framework key, e.g. \"iso-27001\"."
        }
      },
      "additionalProperties": false
    }
    arguments 23 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 9ecca02b1a95c858.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/9ecca02b1a95c858/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/9ecca02b1a95c858/badge.svg)](https://brick.blue/agent/9ecca02b1a95c858?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
70%

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.

_ also on keelgrc.com 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.