_ registry / mcp + a2a streamable-http · checked 45m ago

agentcommunity

https://agentcommunity.org

Registry code: 934e225fb1e78bfb

api record

Agent Community is an open community of the companies, researchers, and developers building the agentic web; it is also the applicant for the proposed .agent top-level domain (pending ICANN approval). Tools: lookup_member looks up one public member by exact display name or slug; get_community_stats returns a roughly-live member count; register_agent pre-registers a .agent name at the DMV (free, non-binding, does not confer domain ownership, and only after an explicit user request); verify_certificate checks the live DMV issuance state of a certificate ID.

endpoint
https://agentcommunity.org/mcp
door code
dc64016ac92a79cd
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 agentcommunity live?
Yes — it answered the hub's last check (checked 45m ago). It answered 99% of checks over the last 30 days.
Is agentcommunity free to use?
Yes — the hub reached it with no key and no payment.
What tools does agentcommunity have?
4 tools: register_agent, lookup_member, verify_certificate, get_community_stats.
Is agentcommunity 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.4%

90 days 99.2%· all time 99.4%

latency
1,173ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1034 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
productivity & business events & memberships
used for
  • look up a community member
  • get community member count
  • pre-register an agent identity name
  • verify an identity certificate
takes → gives
text → data
tools
3 reads1 changes data
_ 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 4 tools
2 open 2 never probed 2 of 4 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.

  • verify_certificate reads open 12h ago

    Verify the live DMV issuance state of a canonical certificate ID. This does not confer domain ownership or mean the .agent TLD exists in DNS.

    mcp-tool

    {
  "type": "object",
  "required": [
    "certificate_id"
  ],
  "properties": {
    "certificate_id": {
      "type": "string",
      "description": "Certificate ID, e.g. MESA-DD6-660J."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • get_community_stats reads open 12h ago

    Get the roughly-live Agent Community member count. The count is cached for up to 20 minutes.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • register_agent changes data unknown never probed

    Pre-register a .agent identity through the DMV. This is free and non-binding, does not confer domain ownership, and should run only after an explicit user request.

    mcp-tool

    {
  "type": "object",
  "required": [
    "agent_name",
    "email",
    "operator_name"
  ],
  "properties": {
    "email": {
      "type": "string",
      "format": "email",
      "description": "Email address for confirmation."
    },
    "agent_name": {
      "type": "string",
      "pattern": "^[a-z0-9](?:[a-z0-9-]*[a-z0-9])?$",
      "maxLength": 63,
      "minLength": 3,
      "description": "Desired name without the .agent suffix."
    },
    "description": {
      "type": "string",
      "maxLength": 500,
      "description": "Optional description."
    },
    "operator_name": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "Person or organization operating the agent."
    }
  },
  "additionalProperties": false
}
    arguments 34 lines
  • lookup_member reads unknown 12h ago

    Look up one public member by exact display name or slug. This is not free-text directory search and returns only minimal public information.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "Exact display name or slug; not free-text search."
    }
  },
  "additionalProperties": false
}
    arguments 15 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 934e225fb1e78bfb.

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

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.