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

said-protocol

https://api.saidprotocol.com

Registry code: d504c7721cce547a

api record

SAID Protocol is on-chain identity infrastructure for autonomous AI agents. Register, verify, and build reputation for your agent on Solana. Free to start.

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

endpoint
https://api.saidprotocol.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 said-protocol live?
Yes — it answered the hub's last check (checked 8h ago). It answered 100% of checks over the last 30 days.
Is said-protocol free to use?
Yes — the hub reached it with no key and no payment.
What tools does said-protocol have?
3 tools: check_token, check_wallet, find_agent.
Is said-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
100%

90 days 100%· all time 100%

latency
310ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ 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.

  • check_token unknown 8h ago

    Two checks on a Solana token mint. (1) Authenticity: if it claims to be a tokenized stock or real-world asset, is it the issuer's real token or an impersonator, and is the backing verifiable? (2) Launch trust: who deployed it, how their previous launches ended, bundling and funding-trail flags, with a pass / caution / fail verdict. Every pass/fail verdict is re-graded at 24h and 7d on a public scoreboard. Free.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "mint"
      ],
      "properties": {
        "mint": {
          "type": "string",
          "pattern": "^[1-9A-HJ-NP-Za-km-z]{32,44}$",
          "description": "Token mint address (base58)"
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • check_wallet unknown 8h ago

    Look up a Solana wallet in SAID Protocol, the identity and reputation registry for AI agents. Returns whether it is a registered and verified agent, its trust score and tier, an allow / review / caution verdict with the reason, and whether the identity has changed hands. Use before sending funds, accepting a job, or trusting a counterparty. Free.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "wallet"
      ],
      "properties": {
        "wallet": {
          "type": "string",
          "pattern": "^[1-9A-HJ-NP-Za-km-z]{32,44}$",
          "description": "Solana wallet address (base58)"
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • find_agent unknown 8h ago

    Search SAID Protocol's registry of AI agents by name, X handle, description or wallet. Returns matching agents with verification status, trust score and profile link. Use to resolve "who is this agent" or to find a counterparty's registered wallet.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1,
          "description": "Max results, default 10"
        },
        "query": {
          "type": "string",
          "maxLength": 80,
          "minLength": 2,
          "description": "Name, @handle, keyword or wallet fragment"
        },
        "verifiedOnly": {
          "type": "boolean",
          "description": "Only return verified agents"
        }
      },
      "additionalProperties": false
    }
    arguments 26 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 d504c7721cce547a.

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