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

agent-card-host-mcp

https://agentcards.site

Registry code: 7504a8ffcf522402

api record
endpoint
https://agentcards.site/mcp
protocol
streamable-http ·2024-11-05
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 agent-card-host-mcp live?
Yes — it answered the hub's last check (checked 5h ago). It answered 100% of checks over the last 30 days.
Is agent-card-host-mcp free to use?
Not measured yet.
What tools does agent-card-host-mcp have?
3 tools: host_quota, host_agent_card, host_credit_intent.
Is agent-card-host-mcp 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
110ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 3 tools
3 never probed 0 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.

  • host_quota unknown never probed

    Look up an account's hosting quota: free uploads used, free remaining, and paid credits available.

    mcp-tool

    {
      "type": "object",
      "required": [
        "owner_account"
      ],
      "properties": {
        "owner_account": {
          "type": "string",
          "description": "Concordium base58 account to query."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • host_agent_card unknown never probed

    Host an A2A AgentCard JSON on agentcards.site. Accepts a card body (string or object) and the owner's Concordium account. Returns the hosted URL + sha256 hash, ready to pin on-chain via the Agent Registry MCP's build_set_agent_uri tool. First 10 uploads per account are free; subsequent uploads cost 100 CCD and return a payment intent instead.

    mcp-tool

    {
      "type": "object",
      "required": [
        "owner_account",
        "card"
      ],
      "properties": {
        "card": {
          "description": "The card JSON. Pass a string of the exact canonical bytes you want hashed (preferred — preserves the bytes the on-chain hash will commit to), OR an object that the service will JSON-serialise."
        },
        "network": {
          "type": [
            "string",
            "null"
          ],
          "description": "Optional label (e.g. 'devnet' / 'mainnet') stored alongside the card for reference."
        },
        "token_id": {
          "anyOf": [
            {
              "type": "string",
              "pattern": "^[0-9]+$"
            },
            {
              "type": "integer",
              "minimum": 0
            },
            {
              "type": "null"
            }
          ],
          "description": "Optional — when the agent has already been minted, pass its token_id so the hosted card can be cross-referenced."
        },
        "agent_uri": {
          "type": [
            "string",
            "null"
          ],
          "description": "Optional — the agent_uri the card will be referenced by on-chain. Surfaced in the per-owner card index for later inspection."
        },
        "owner_account": {
          "type": "string",
          "description": "Concordium base58 account that owns / will own the agent NFT."
        }
      },
      "additionalProperties": false
    }
    arguments 47 lines
  • host_credit_intent unknown never probed

    Request a paid-tier credit purchase. Returns a memo + service-receive account on the requested network; the user sends 100 CCD with that memo and the chain watcher tailing that network grants one upload credit when the transfer finalises. Returns 503-equivalent if the operator hasn't configured a service-receive wallet on that network yet.

    mcp-tool

    {
      "type": "object",
      "required": [
        "account"
      ],
      "properties": {
        "account": {
          "type": "string",
          "description": "Concordium base58 account that will receive the credit."
        },
        "network": {
          "type": [
            "string",
            "null"
          ],
          "description": "Network to pay on (devnet / testnet / mainnet). Omit to let the service pick any network that's configured."
        }
      },
      "additionalProperties": false
    }
    arguments 20 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 7504a8ffcf522402.

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