api-evangelist
Registry code: d9128ce15e0bbc25
Sixteen years of API research plus a governance compute layer, as tools, prompts, and resources. LIGHTER ENDPOINTS: this endpoint lists all 82 tools. If you only need one kind of work, connect to a task-scoped toolset instead — same tools, same auth, a fraction of the context: https://mcp.apievangelist.com/mcp/research (31 tools: sixteen years of API research — posts, papers, videos, conversations, areas, tags, building blocks, tools, services, solutions, timeline, feeds); https://mcp.apievangelist.com/mcp/governance (43 tools: the governance compute layer — validate, coverage, scorecard,…
- endpoint
- https://mcp.apievangelist.com/mcp
- door code
- ac16c8c321141a52
- protocol
- MCP ·0.3
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is api-evangelist live?
- Yes — it answered the hub's last check (checked 35m ago). It answered 100% of checks over the last 30 days.
- Is api-evangelist free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does api-evangelist have?
- 6 tools: Search sixteen years of API research, Read a story, area or paper, Find services and reach a human, Profile a company or a standard, Assemble API governance building blocks, Validate, score and govern APIs.
- Is api-evangelist 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.
90 days 100%· all time 100%
last good check
of 6 tools
- used for
- score an api's maturity
- compare two openapi versions for breaking changes
- find api tools and vendors
- generate code samples for an api
- search api research articles
- takes → gives
- code, text → data, code, text
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.
through this hub
successful
what callers paid
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.
search-the-network unknown never probed
Federated search across 5,100+ stories, 77 topic areas, governance building blocks, papers, conversations, videos and the tag taxonomy, with related-content discovery weighted so rare tags matter most. Free, no key required.
read-research unknown never probed
Retrieve any single item the network publishes: a post, a topic area with its resolved related graph, a paper, a conversation, a video or the API vocabulary. Summaries and metadata are free; full content bodies and the curated multi-source topic guide are Pro.
find-where-api-evangelist-helps unknown never probed
What API Evangelist offers a team, the first-party services catalog, the third-party solutions registry, and the way to engage a person directly. Free and unmetered — finding out how to work with us is not a paid feature.
company-and-standard-intelligence unknown never probed
Company insights across measured dimensions — gaps, peers, whitespace and demand signals — alongside adoption, coalition and repository intelligence for the standards the network measures. Paid.
governance-building-blocks unknown never probed
2,400+ reusable building blocks across five types — guidance, rules, policies, standards and strategies — the raw material for a governance program, addressable individually or as a starter kit.
validate-and-govern-apis unknown never probed
Run an OpenAPI through validation, coverage, scorecards, version diffs, overlays, waiver reconciliation, certification and estate-wide governance reports — plus agent-readiness checks, exported agent rules and MCP tool forging. Paid.
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idd9128ce15e0bbc25.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/d9128ce15e0bbc25/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/d9128ce15e0bbc25?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.