Meta Agent Tools

{
  "name": "Meta Agent Tools",
  "description": "Find MCP servers, skills, plugins and OKF knowledge bundles for your task. Compare sources and connections. Free to browse, to submit and to read through the API.",
  "url": "https://agentalog.com",
  "provider": {
    "organization": "Meta Agent Tools",
    "url": "https://agentalog.com",
    "email": "contato@agentalog.com"
  },
  "documentationUrl": "https://agentalog.com/llms.txt",
  "protocol": "mcp",
  "protocolUrl": "https://modelcontextprotocol.io",
  "interfaces": [
    {
      "transport": "streamable-http",
      "url": "https://agentalog.com/mcp"
    }
  ],
  "capabilities": {
    "streaming": true,
    "pushNotifications": false,
    "authentication": "none"
  },
  "defaultInputModes": [
    "application/json"
  ],
  "defaultOutputModes": [
    "application/json",
    "text/markdown"
  ],
  "skills": [
    {
      "id": "search_bundles",
      "name": "search_bundles",
      "description": "Search the index of OKF bundles: free text over name, tagline, description and origin; filter by provenance (github|domain), repository, version, language, license, root type or concept count; search root concept text. Paginate with limit/offset. Only `live` bundles. Free text matches the name, the tagline, the description and the origin identifier (`owner/repo:path` or the bundle URL). No `total` on purpose: `GET /api/okf/stats` has it.",
      "endpoint": "GET /api/bundles"
    },
    {
      "id": "get_bundle",
      "name": "get_bundle",
      "description": "One bundle's card: root index.md URL, version, concept count, provenance and repository signal. `live` and `low` (example or fixture bundles kept out of the search) both answer here.",
      "endpoint": "GET /api/bundles/:id"
    },
    {
      "id": "index_stats",
      "name": "index_stats",
      "description": "Size of the index by provenance and when it last changed.",
      "endpoint": "GET /api/okf/stats"
    },
    {
      "id": "feed_find",
      "name": "feed_find",
      "description": "Does this site publish a feed? Answers with every feed known for a domain \u2014 the question a reader or an agent actually asks. Find feeds by text, format, language and availability. Filter and text search run in the SAME full-text query: values inside one parameter are OR'd, different parameters are AND'd. Without `q` the order is by newest in the index (`recentes`) and `next_cursor` is a keyset \u2014 follow `next` to walk everything. With `q` the order is relevance and paging is by `offset`. We index and link; the feeds belong to whoever publishes them.",
      "endpoint": "GET /api/feeds"
    },
    {
      "id": "feed_posts",
      "name": "feed_posts",
      "description": "What has this feed published? The posts of one feed as our queue read them \u2014 title, date, author, summary, categories and enclosure, without the body. Find the feed first (feed_find or feed_search); this takes an id from this index, never a URL. Up to 40 posts, in the order the feed publishes them, WITHOUT the body \u2014 the body of one post comes from `/items/:ord`. It is OUR copy, read on our own schedule \u2014 not the live feed and not a proxy: the only thing this endpoint accepts is an id from this index, never a URL. `lido_em` says when we read it. Empty list when the feed has not been read yet.",
      "endpoint": "GET /api/feeds/:id/items"
    },
    {
      "id": "feed_post",
      "name": "feed_post",
      "description": "Read one post whole: the body in Markdown (`conteudo`) and the author's formatting as safe HTML (`conteudo_html`), plus the link to the original. `ord` comes from feed_posts; 0 is the newest. Two bodies for the same post, both from the copy we stored when we READ the feed \u2014 a request never fetches the site: `conteudo_html` keeps the author's formatting through an allowlist (only known tags and attributes survive; script, style, iframe and event handlers are dropped with their content), and `conteudo` is the same text as Markdown \u2014 the shape an agent usually wants. Neither can carry script. 404 when the feed or the position is unknown.",
      "endpoint": "GET /api/feeds/:id/items/:ord"
    },
    {
      "id": "feed_search",
      "name": "feed_search",
      "description": "Search the feed index by text and filters: format, audio/video, community, namespace and year of the newest item. Find feeds by text, format, language and availability. Filter and text search run in the SAME full-text query: values inside one parameter are OR'd, different parameters are AND'd. Without `q` the order is by newest in the index (`recentes`) and `next_cursor` is a keyset \u2014 follow `next` to walk everything. With `q` the order is relevance and paging is by `offset`. We index and link; the feeds belong to whoever publishes them.",
      "endpoint": "GET /api/feeds"
    },
    {
      "id": "mcp_index_signals",
      "name": "mcp_index_signals",
      "description": "Does this MCP server still answer, with which access, and is its repository alive? What independent MCP indexes measured about one listing of this catalog, each credited with its license. Take the id from list_listings. A signal belongs to a listing only when it is the SAME object: the name in the official MCP registry, the exact remote endpoint URL or the GitHub `owner/repo`, in that order. A shared domain never matches \u2014 two servers on one host are different products. Up to 20 signals, one per index and record.",
      "endpoint": "GET /api/indices/sinais"
    },
    {
      "id": "mcp_index_search",
      "name": "mcp_index_search",
      "description": "Browse what independent MCP indexes measured, including servers this catalog does not list yet (casou=0). Newest change first. `casou=0` is what the indexes know and the catalog does not \u2014 the list to look at before submitting a server. Filters are AND'd.",
      "endpoint": "GET /api/indices/itens"
    },
    {
      "id": "a2a_agent_search",
      "name": "a2a_agent_search",
      "description": "Find A2A agents \u2014 agents that publish an AgentCard \u2014 by text, health, protocol version, registry, skill tag or publisher. Each row carries the key for a2a_agent and the license of every registry that lists it. Collected from public A2A registries and served as it comes \u2014 no review queue hides a record; quality is the order, never visibility. One row per agent, merged across the registries that list it: `fontes` says which, and `creditos` carries each one's license, which travels with the data. Values inside one parameter are OR'd, different parameters are AND'd. Cached for 60 seconds. A MAT catalog read, served by the index host `https://api.agentalog.com`; this host forwards the call there.",
      "endpoint": "GET /api/a2a/agents"
    },
    {
      "id": "a2a_agent",
      "name": "a2a_agent",
      "description": "Read one A2A agent: every skill its card declares, capabilities, protocol version, health, documentation and the registries that list it, with their licenses. Take the key from a2a_agent_search. The same row as the list plus what the card declares: every skill, the `capabilities` object, the protocol version as written, the documentation and icon URLs, and when we first saw it. Cached for 60 seconds; a MAT catalog read, like the list.",
      "endpoint": "GET /api/a2a/agents/:chave"
    },
    {
      "id": "briefings_topics",
      "name": "briefings_topics",
      "description": "Which engineering topics have curated briefings, how many links each has and the newest links across all of them. Each link comes with its source, source type and a two-line summary. Topics are public bookmark folders (CUDA, inference, RAG, agents\u2026). Each item is a post someone saved, its main source, the source type and a two-line summary in English and Portuguese. `?resumo=1` returns only `total` and each topic's `slug` and `total`. 404 until the first publication.",
      "endpoint": "GET /api/briefings"
    },
    {
      "id": "briefings_links",
      "name": "briefings_links",
      "description": "Curated engineering links filtered by topic and source type (paper, repo, model, dataset, demo, video, docs, article, post), 20 per page, with the count of each filter value. Values inside one parameter are OR'd; the two parameters are AND'd. Unknown values are ignored. Follow `_links.next` to walk everything.",
      "endpoint": "GET /api/briefings/itens"
    },
    {
      "id": "api_index",
      "name": "api_index",
      "description": "Self-describing index: the whole API surface, with quota and quickstart.",
      "endpoint": "GET /api/"
    },
    {
      "id": "health",
      "name": "health",
      "description": "Liveness and the commit deployed right now \u2014 it is how the smoke waits for its own deploy.",
      "endpoint": "GET /api/health"
    },
    {
      "id": "create_guest",
      "name": "create_guest",
      "description": "Creates a guest mr_\u2026 Asks for no e-mail. Publishing a listing is what requires an account (or a payment). At most 20 new guests per network per hour; a browser that already has one gets it back from the `mr_guest` cookie.",
      "endpoint": "POST /api/guest"
    },
    {
      "id": "list_listings",
      "name": "list_listings",
      "description": "Public mosaic of live MCP servers, skills, plugins and OKF knowledge bundles. `live` listings first and the `low` tail (few stars or no clear license) after them in every order \u2014 `low=0` leaves the tail out. To walk everything, follow `next`: without `q` it is a cursor (`next_cursor`, keyset on the order's index) and has no ceiling; every listing also has an HTML page at `/l/:id` and the shards of `/sitemap-listings.xml` list them all. `q` runs on a full-text index (FTS5, bm25) kept in the same transaction as every text write. With `q` and `low=0`, `low_count` says how many `low` listings the filter left out \u2014 LIKE with a cap of 200. The query is mapped onto kind/topic/transport filters unless `interpret=0`.",
      "endpoint": "GET /api/listings"
    },
    {
      "id": "list_mcp_servers",
      "name": "list_mcp_servers",
      "description": "MCP subregistry (GET /v0.1/servers). Only live kind=mcp. Only `kind=mcp` and only `live`. It is the route a generic MCP client knows how to read without knowing this product. `GET /v0/servers` is an alias of the same resource, kept for whoever already pointed there \u2014 this is the canonical URL.",
      "endpoint": "GET /v0.1/servers"
    },
    {
      "id": "get_listing",
      "name": "get_listing",
      "description": "One listing's page. The owner sees their own even when pending or hidden.",
      "endpoint": "GET /api/listings/:id"
    },
    {
      "id": "get_listing_readme",
      "name": "get_listing_readme",
      "description": "README collected for a listing (R2). Only when get_listing carries readme_api; 404 when none was stored. The text lives in R2 (`mural-coleta`). This call does not write and does not fetch GitHub. Same visibility as the listing page. Call it only when the listing page carries `readme_api`: a page without it has no README collected, and this route answers 404.",
      "endpoint": "GET /api/listings/:id/readme"
    },
    {
      "id": "listing_history",
      "name": "listing_history",
      "description": "Timeline of the listing's repository: last events (abandono = no push for 12 months, sumiu, renomeado, readme_mudou, manifesto_mudou), newest first; empty when nothing changed since the series began. The listing page carries the same list as `historico`; updates may be cached for up to 15 minutes. An empty list means no change since the series began \u2014 the listing still exists. Stale means no push for 12 months. Reading this endpoint does not refresh the record.",
      "endpoint": "GET /api/listings/:id/history"
    },
    {
      "id": "go_listing",
      "name": "go_listing",
      "description": "302 hop to the listing's origin (counts a visit). Counts at most 1 visit per owner per day. The `X-Visit-Counted` header says whether this call counted \u2014 it is how the client knows without counting twice.",
      "endpoint": "GET /api/go/:id"
    },
    {
      "id": "like_listing",
      "name": "like_listing",
      "description": "Likes the listing; DELETE undoes it. Calling again does not add up: the counter counts people.",
      "endpoint": "POST /api/listings/:id/like"
    },
    {
      "id": "list_comments",
      "name": "list_comments",
      "description": "Comments on a live listing. With a credential on the call, each comment of yours comes with `mine: true`.",
      "endpoint": "GET /api/listings/:id/comments"
    }
  ],
  "discovery": {
    "openapi": "https://agentalog.com/openapi.json",
    "llms": "https://agentalog.com/llms.txt",
    "okf": "https://agentalog.com/okf/index.md",
    "numbers": "https://agentalog.com/api/vitrine",
    "partnerships": "https://agentalog.com/api/partners",
    "api_catalog": "https://agentalog.com/.well-known/api-catalog",
    "x402": "https://agentalog.com/.well-known/x402",
    "pricing": "https://agentalog.com/pricing",
    "docs": "https://agentalog.com/docs"
  },
  "updated": "2026-10-03"
}