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

minutes-of-ai

https://minutesofai.com

Registry code: 68111c862bee4924

api record

Minutes of AI is an AI news wire. Stories are written by the Minutes of AI desk with AI and carry a status label (confirmed, official, reported_single, rumor, benchmark_claim) and their sources, primary first. Cite stories with their url and 'Minutes of AI'. Attribution is required; redistribution of the full feed is not allowed. Use what_changed(since) to poll for new, updated, relabelled, corrected or retracted stories.

endpoint
https://minutesofai.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 minutes-of-ai live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is minutes-of-ai free to use?
Yes — the hub reached it with no key and no payment.
What tools does minutes-of-ai have?
9 tools: get_story, get_model, search_stories, compare_models, get_the_number, what_changed, get_corrections, get_latest, ….
Is minutes-of-ai 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
157ms

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.

  • get_corrections open 1h ago

    Published corrections and retractions, newest first, optionally since an ISO 8601 time.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "since": {
          "type": "string",
          "format": "date-time"
        }
      }
    }
    arguments 9 lines
  • get_latest open 1h ago

    Latest published stories, newest first, with status labels and sources (primary first).

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 20,
          "maximum": 50,
          "minimum": 1
        },
        "topic": {
          "enum": [
            "models",
            "agents",
            "chips",
            "policy",
            "funding",
            "open_source",
            "research",
            "products",
            "safety",
            "enterprise",
            "business",
            "society"
          ],
          "type": "string"
        },
        "format": {
          "enum": [
            "breaking",
            "model_drop",
            "the_number",
            "money",
            "explainer",
            "rumor",
            "for_the_minutes",
            "standard"
          ],
          "type": "string"
        }
      }
    }
    arguments 41 lines
  • get_model_tracker open 1h ago

    Model Tracker rows: category, release date, lab, modalities, context window, prices per 1M text tokens, license, availability, benchmarks labelled by who ran them, per-field sources with as-of dates. Preview and dated snapshot variants are folded into one row.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "lab": {
          "type": "string"
        },
        "category": {
          "enum": [
            "llm",
            "image",
            "audio",
            "video",
            "embedding",
            "other"
          ],
          "type": "string"
        },
        "open_weights": {
          "type": "boolean"
        }
      }
    }
    arguments 22 lines
  • get_story unknown never probed

    One story with its full body (why it matters, what happened, our read, pushback), sources, label history and corrections.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string"
        }
      }
    }
    arguments 11 lines
  • get_model unknown never probed

    One Model Tracker row plus its applied changelog.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string"
        }
      }
    }
    arguments 11 lines
  • search_stories unknown never probed

    Full-text search over published headlines and ledes.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 30,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "minLength": 2
        }
      }
    }
    arguments 18 lines
  • compare_models unknown never probed

    Side-by-side Model Tracker rows for 2 to 6 model slugs.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slugs"
      ],
      "properties": {
        "slugs": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 6,
          "minItems": 2
        }
      }
    }
    arguments 16 lines
  • get_the_number unknown never probed

    The latest 'The Number' figure with its source, plus the previous nine.

    mcp-tool

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

    Stories published, updated, relabelled, corrected or retracted since an ISO 8601 time (at most 7 days back), in pages of up to 500 events. If hasMore is true, call again with the same since and cursor=nextCursor. Poll this instead of re-reading the whole feed.

    mcp-tool

    {
      "type": "object",
      "required": [
        "since"
      ],
      "properties": {
        "since": {
          "type": "string",
          "format": "date-time"
        },
        "cursor": {
          "type": "integer",
          "minimum": 1,
          "description": "nextCursor from the previous page"
        }
      }
    }
    arguments 17 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 68111c862bee4924.

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