_ registry / mcp http-sse · checked 6h ago

agentic-kit

https://agentic-kit.dev

Registry code: 59c70b1776f9d23e

api record

Agentic Kit is the product shell for eve (Vercel): inspect (Aletheia portraits), gate (aletheia-cli authority diff), stamp (Kit Certified).

Prefer MCP resources over tools when attaching context: agentic-kit://docs/{id}, agentic-kit://policy-packs/{id}, agentic-kit://library/full.

endpoint
https://agentic-kit.dev/api/mcp
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 agentic-kit live?
Yes — it answered the hub's last check (checked 6h ago). It answered 97% of checks over the last 30 days.
Is agentic-kit free to use?
Yes — the hub reached it with no key and no payment.
What tools does agentic-kit have?
5 tools: docs.get, packs.get, docs.list, library.get, packs.list.
Is agentic-kit 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
97.1%

90 days 98.2%· all time 98.2%

latency
1,951ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 331 checks · signed record
  • down → live
  • degraded → down· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • read agentic kit documentation
  • get blast-radius policy packs for agents
  • fetch full agentic kit corpus
takes → gives
text → text
tools
5 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 5 tools
3 open 2 never probed 3 of 5 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.

  • docs.list reads open 6h ago

    List every Agentic Kit doc id (honesty contract, CLI, CI, Kit Certified, and more). Prefer resources/list and agentic-kit://docs/{id} when attaching context; call docs.get only when you need the body as a tool result.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • library.get reads open 6h ago

    Fetch the complete Agentic Kit corpus (llms-full.txt) in one call. Prefer resource agentic-kit://library/full when attaching context; use this tool only when the client lacks resource support.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • packs.list reads open 6h ago

    List published blast-radius policy pack ids for eve agents. Prefer resources/list and agentic-kit://policy-packs/{id}; call packs.get when you need the JSON as a tool result.

    mcp-tool

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

    Fetch one Agentic Kit doc body by id (markdown/plain text). Prefer resource agentic-kit://docs/{id} when your client can attach resources; use this tool when you need the text in the tool channel.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "pattern": "^[a-z0-9-]+$",
          "description": "Doc id slug from docs.list. Examples: 'honesty-contract', 'kit-certified', 'cli', 'ci'."
        }
      }
    }
    arguments 14 lines
  • packs.get reads unknown 28h ago

    Fetch one policy pack JSON by id (blast-radius thresholds per domain). Prefer resource agentic-kit://policy-packs/{id} when attaching context.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "pattern": "^[a-z0-9-]+$",
          "description": "Policy pack id from packs.list. Examples: 'support-bot', 'payments-high', 'design-tools'."
        }
      }
    }
    arguments 14 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 59c70b1776f9d23e.

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

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.