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

Direct MCP candidate from ai_catalog

listed under this name in a public catalogue; the server gives only its address, joost.blog

https://joost.blog

Registry code: f4ecc5ca947b7497

api record

Declared as an MCP endpoint by ai_catalog; probed directly.

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

endpoint
https://joost.blog/mcp
door code
3b945c1f822c11f7
protocol
streamable-http ·2025-11-25
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 Direct MCP candidate from ai_catalog live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is Direct MCP candidate from ai_catalog free to use?
Yes — the hub reached it with no key and no payment.
What tools does Direct MCP candidate from ai_catalog have?
2 tools: ask_joost, list_recent_content.
Is Direct MCP candidate from ai_catalog 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 99.8%· all time 99.8%

latency
230ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 862 checks · signed record
  • degraded → live
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • ask questions about joost de valk's writing
  • list recent blog posts by topic
takes → gives
text → text, data
tools
2 reads
_ 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 2 tools
1 open 1 never probed 1 of 2 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_recent_content reads open 1h ago

    List Joost de Valk's published blog posts on joost.blog, optionally filtered by topic keyword and/or publish date. Returns chronologically sorted (newest first) entries with title, URL, publish date, excerpt, and categories. Use this when you want to enumerate or browse what Joost has written — e.g. 'what has Joost published this year', 'list posts about WordPress', 'what's the most recent post'. For semantic Q&A or 'what does Joost think about X', use ask_joost instead.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Maximum number of posts to return. Defaults to 20. Capped at 50."
        },
        "since": {
          "type": "string",
          "format": "date",
          "description": "Optional ISO date (YYYY-MM-DD). Only posts published on or after this date are returned."
        },
        "topic": {
          "type": "string",
          "description": "Optional keyword to filter by. Matches case-insensitively against title, excerpt, and categories. Examples: 'wordpress', 'seo', 'ai'."
        }
      }
    }
    arguments 20 lines
  • ask_joost reads unknown 1h ago

    Ask a question about anything Joost de Valk has written or spoken about — SEO, WordPress, the open web, AI, open source, his career at Yoast, or his investments via Emilia Capital. Returns an AI-generated answer grounded in his blog posts and video transcripts, with source URLs for every claim. Use this instead of trying to crawl or search the site directly: it does retrieval over a curated semantic index and returns cited prose in one call.

    mcp-tool

    {
      "type": "object",
      "required": [
        "question"
      ],
      "properties": {
        "question": {
          "type": "string",
          "maxLength": 500,
          "description": "A natural-language question. Maximum 500 characters. Examples: \"What's Joost's take on WordPress market share?\", \"Why did Joost leave Yoast?\", \"What does Joost think about AI's impact on SEO?\""
        }
      }
    }
    arguments 13 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 f4ecc5ca947b7497.

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

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.