Meta Agent Tools

{
  "name": "Meta Agent Tools",
  "description": "Find tools for your agent by task or service. Compare sources, connection methods and installation requirements. Browsing and submissions are free while billing is off.",
  "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. With `q`, `total` is the exact number of matches, including when the requested page is empty.",
      "endpoint": "GET /api/indices/itens"
    },
    {
      "id": "check_tool",
      "name": "check_tool",
      "description": "Before installing a remote MCP server, check its address: signals from the address itself (consumer tunnel, no TLS), the catalog listings with that address or host and their security level, and facts about its domain. Never visits the address. Send the endpoint URL. The answer never contacts that address: it reads what our weekly visits measured and what our domain data knows. `sinais_do_endereco` comes from the address alone (consumer tunnel, `http://` without TLS). `registros` lists the catalog listings with this exact address first (`exato: true`), then up to 20 others on the same host, each with its level and signals; `mesmo_host` counts them all. `dominio` has the facts about the host's domain. An address outside the catalog answers `no_catalogo: false` and `registrar`: submit it to get it reviewed. Cached for 5 minutes.",
      "endpoint": "GET /api/check"
    },
    {
      "id": "listing_security",
      "name": "listing_security",
      "description": "Read a remote MCP server or SKILL.md review before installing. MCP: server, domain, tools and measured signals. Skill: static findings with file, line, excerpt and context; no command execution or referenced-script review. Unread skills stay unchecked. Read the limits in aviso. Take the id from list_listings. We visit remote MCP servers: `initialize` and `tools/list`, without credentials or tool calls, again 7 days after a success. A failure needs a second check. MCP signals: dns_morto, sem_https, tls_invalido, tunel, nao_responde, nao_mcp, texto_suspeito, redireciona_fora, repo_arquivado, repo_parado, dominio_recente, login, bloqueado. For skills, `tipo: skill` identifies a static SKILL.md review. It flags secret reads, download-and-execute commands, external uploads, invisible characters, long encoded text and broad allowed-tools. `revisao.achados` supplies the path, original line, excerpt and context. Examples and prohibitions do not raise the level. Excerpts hide sensitive values. The review does not run commands or follow references. Supported source: public raw.githubusercontent.com SKILL.md. Watched, visited, starred and new skills get priority within the shared GitHub governor and a daily cap. Unread or unsupported skills remain explicitly unchecked. Local MCP servers and plugins answer `nao_remoto`. No request fetches a third-party source. Cached for 5 minutes.",
      "endpoint": "GET /api/listings/:id/security"
    },
    {
      "id": "listing_tools",
      "name": "listing_tools",
      "description": "The tools and instructions a remote MCP server announced at its last check, with what they mention doing and any suspicious text. 404 tools_not_read when the server was not read yet. The announced manifest, normalized: each tool's name, title, description (up to 4,000 characters), input schema (null above 8,000 characters) and protocol annotations, plus the server instructions. `capacidades` and `suspeitas` come from the current rules, applied when you read. Reading this endpoint never contacts the server. Cached for 5 minutes.",
      "endpoint": "GET /api/listings/:id/tools"
    },
    {
      "id": "list_watched_tools",
      "name": "list_watched_tools",
      "description": "The MCP servers and skills the account watches, with their review level, slots and offers. Daily checks cover MCP tools, state, level, country and version. Supported skills cover changes in SKILL.md text and review signals. Source quotas can delay a check; read proxima_em and verificado_em. The e-mail goes to the verified account address and includes an unsubscribe link. Wallet-only owners follow changes through the API.",
      "endpoint": "GET /api/me/vigia"
    },
    {
      "id": "watch_tool",
      "name": "watch_tool",
      "description": "Watch a remote MCP or supported SKILL.md. Daily schedule, subject to source quota; account e-mail for changes. Skills cover text and review signals, not execution. 3 free slots per owner; 402 for more. Unsupported sources are rejected before payment. Choose a live remote MCP or a skill with a supported public raw.githubusercontent.com SKILL.md, after skill collection is enabled. Unsupported skills are rejected before payment. Watching again is a no-op (`ja_vigiado`). Pay the 402 with x402 or prepaid credit and repeat the request. Slots last 30 days with no automatic renewal. Skills do not enter the Claude Code MCP allowlist.",
      "endpoint": "POST /api/me/vigia"
    },
    {
      "id": "unwatch_tool",
      "name": "unwatch_tool",
      "description": "Stop watching a server; its slot becomes free.",
      "endpoint": "DELETE /api/me/vigia/:id"
    },
    {
      "id": "buy_watch_plan",
      "name": "buy_watch_plan",
      "description": "Buy watch slots for 30 days, no auto-renewal: vaga (1 server), equipe (50) or empresa (500); prices in the pricing tool. Answers 402 with the price; pay with x402 or prepaid credit and repeat. Answers 402 with the price; pay with x402 or prepaid credit and repeat the request. Passes last 30 days with no automatic renewal; a new purchase adds slots.",
      "endpoint": "POST /api/me/vigia/plano"
    },
    {
      "id": "claude_code_allowlist",
      "name": "claude_code_allowlist",
      "description": "The watch list as Claude Code managed settings (allowedMcpServers, deniedMcpServers) and claude mcp add commands. `managed_settings` goes into a Claude Code managed settings source (see `docs`). `allowManagedMcpServersOnly` restricts user-added servers to this list. Checked servers rated as `risco` go to `deniedMcpServers`. The exact URL and that URL followed by `?*` permit the checked route with optional query parameters. Expired or unchecked items stay out. `comandos` has one quoted `claude mcp add` command per allowed server.",
      "endpoint": "GET /api/me/vigia/claude-code"
    },
    {
      "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"
    }
  ],
  "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",
    "agent_access": "https://agentalog.com/.well-known/agent-access.json",
    "x402": "https://agentalog.com/.well-known/x402",
    "pricing": "https://agentalog.com/pricing",
    "docs": "https://agentalog.com/docs"
  },
  "updated": "2026-10-08"
}