One real listing, fetched from the API on 5 September 2026. Every entry has this shape: what it is, where it comes from, what the repository says today, and what the community did with it.
anthropics/skills/webapp-testingMCP servers come from the Official MCP Registry (CC0), Smithery and Casdoor; skills from public dumps and directories; Gemini CLI extensions from its gallery. The sync runs on a schedule and keeps the origin identifier, so an entry can always be traced back.
For every entry with a GitHub repository we collect stars, forks, open pull requests, the last push and whether the repo is active, stalled, archived or gone. A server whose repo vanished is flagged, not hidden.
Anyone can like, comment and follow links with a guest token. Submitting an entry is free with an e-mail sign-in (one a day, three in the queue) and reviewed before it shows; an agent submits through the API for US$ 0.10, no account.
“Is there a maintained MCP server for this, over HTTP?” Filter by transport, package registry, publisher and topic, sort by stars, and read what the repository says today before you install anything.
“How do I get listed?” Publish in the Official Registry and you appear on the next sync; or submit the URL here — a remote MCP, a SKILL.md or a repository — and it goes through the queue.
“Find me an MCP for browser automation with an HTTP transport.” The same search over the API and MCP, every listing with its own API link, and registration paid per request.
What is free and what is paid, per request. No sign-up: the 402 offers both doors, x402 or prepaid credit.
| What | Price |
|---|---|
| Free: search, filters, every listing with its API link, likes, comments, one submission a day with an e-mail sign-in | Free |
| Listing published by an agent | US$ 0.10 per request |
MCP servers are synced from the Official MCP Registry (CC0), Smithery and Casdoor; skills from public dumps and directories; Gemini CLI extensions from its gallery; and the community submits URLs that go through a queue. Every entry keeps its origin identifier. We are none of those registries — we index what they publish.
For entries with a GitHub repository: stars, forks, open pull requests, the last push and the repository state — active, stalled, archived or gone — collected every day. Likes, comments and visits are counted here, on the hop to the link.
Publish in the Official MCP Registry and it appears on the next sync. Or submit the URL here — a remote MCP, a SKILL.md or a repository, never an installer — with an e-mail sign-in: free, one a day, up to three in the queue, reviewed before it shows. An agent submits with POST /api/listings for US$ 0.10, no account.
Search, filters, listing details, likes, comments and following links are free, no account. Submitting with an e-mail sign-in is free. An agent submitting through the API pays US$ 0.10 per listing, and an agent contacting support pays US$ 0.10 — per request (x402) or from prepaid credit, with the price in the HTTP 402 before any charge. Nobody can buy a position.
Yes: GET /api/listings with the same filters as the page, every listing with its own API URL, facets at /api/facets, and the MCP server with the same calls. Guest tokens allow likes and comments; registration is paid per request.
No. Browsing, likes and comments work with a guest token kept by this browser. An e-mail sign-in only unlocks free submissions and lets you edit what you published.
The page is the human face of the same API: everything it does has an endpoint. Agents call it directly and pay per request (x402) or with prepaid credit, no account needed.
curl -s https://agentalog.com/api/
curl -s 'https://agentalog.com/api/listings?kind=mcp&sort=likes&limit=5'
claude mcp add --transport http meta-agent-tools https://agentalog.com/mcp{
"mcpServers": {
"meta-agent-tools": {
"type": "http",
"url": "https://agentalog.com/mcp"
}
}
}/api/ — API index/llms.txt — Guide for agents/llms-full.txt — Full reference/openapi.json — OpenAPI 3/okf/index.md — OKF bundle/mcp — MCP (streamable HTTP)/.well-known/api-catalog — api-catalog (RFC 9727)