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

the-ai-record

https://the-ai-record.com

Registry code: 2890fa3eeb88a2ca

api record

The AI Record is a cited archive of what people at organizations have said about how they use AI, why, and with what results. Use it instead of recalling quotes from memory.

Rules: quote passages verbatim or not at all. With each passage give the speaker, role, organization, date and source, the evidence grade (A filing or earnings call, B the organization's own post or talk, C interview or press, D third-party estimate), whether it has been checked against the source, whether the organization sells AI tools, and the passage's own link. Weigh sources by grade and by the speaker's role (an…

endpoint
https://the-ai-record.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 the-ai-record live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is the-ai-record free to use?
Yes — the hub reached it with no key and no payment.
What tools does the-ai-record have?
9 tools: get_topic, get_person, check_attribution, search_passages, get_passage, get_organization, list_organizations, archive_stats, ….
Is the-ai-record 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
285ms

last good check

priced tools
0

of 9 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

_ what it can do 9 tools
3 open 6 never probed 3 of 9 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.

  • list_organizations open 1h ago

    Every organization in the archive, with sector, passage counts and whether it sells AI tools.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "ai_vendor": {
          "type": "boolean",
          "description": "true: only organizations that sell AI tools; false: only those that do not."
        }
      }
    }
    arguments 9 lines
  • archive_stats open 1h ago

    How many passages, organizations and speakers the archive holds, and how many passages are checked.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • list_topics open 1h ago

    Every question topic the archive files passages under, with a summary and passage count.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_topic unknown never probed

    One topic and its passages, clearest first.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "The topic id or title (see list_topics)."
        },
        "limit": {
          "type": "integer",
          "default": 15,
          "maximum": 50,
          "minimum": 1,
          "description": "How many passages to return (1 to 50)."
        }
      }
    }
    arguments 19 lines
  • get_person unknown never probed

    One person quoted in the archive: role, organization, why their word counts, and what they said.

    mcp-tool

    {
      "type": "object",
      "required": [
        "person"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 15,
          "maximum": 50,
          "minimum": 1,
          "description": "How many passages to return (1 to 50)."
        },
        "person": {
          "type": "string",
          "description": "The person id or name."
        }
      }
    }
    arguments 19 lines
  • check_attribution unknown never probed

    Check a quotation about AI attributed to someone: looks in the archive's checked list of circulating lines, then for passages with the same wording. No match means the archive does not hold it, not that the quote is false.

    mcp-tool

    {
      "type": "object",
      "required": [
        "quote"
      ],
      "properties": {
        "quote": {
          "type": "string",
          "description": "The quotation as it circulates."
        },
        "speaker": {
          "type": "string",
          "description": "Who it is attributed to (optional)."
        }
      }
    }
    arguments 16 lines
  • search_passages unknown never probed

    Find verbatim passages where people at organizations described how they use AI, ranked by relevance with checked passages and the clearest statements first. Each result has speaker, role, organization, date, source, evidence grade, verification status and its own link. Returns nothing when the archive holds nothing on point.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "grade": {
          "type": "string",
          "description": "Only these grades, comma separated, e.g. \"A,B\"."
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 25,
          "minimum": 1,
          "description": "How many passages to return (1 to 25)."
        },
        "query": {
          "type": "string",
          "description": "The question or subject in plain words, e.g. \"agents doing code review\"."
        },
        "topic": {
          "type": "string",
          "description": "Only passages on this topic id (see list_topics)."
        },
        "person": {
          "type": "string",
          "description": "Only passages from this speaker (id or name)."
        },
        "organization": {
          "type": "string",
          "description": "Only passages about this organization (id or name), e.g. \"Stripe\"."
        },
        "verified_only": {
          "type": "boolean",
          "description": "Only passages checked against the source."
        }
      }
    }
    arguments 39 lines
  • get_passage unknown never probed

    One passage by its id (the last part of its /passages/ URL), with its full citation.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "The passage id."
        }
      }
    }
    arguments 12 lines
  • get_organization unknown never probed

    One organization: profile, size and results from its filings (each with its source), its people, and its passages, strongest evidence first.

    mcp-tool

    {
      "type": "object",
      "required": [
        "organization"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 15,
          "maximum": 50,
          "minimum": 1,
          "description": "How many passages to return (1 to 50)."
        },
        "organization": {
          "type": "string",
          "description": "The organization id or name, e.g. \"shopify\"."
        }
      }
    }
    arguments 19 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 2890fa3eeb88a2ca.

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

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.