meta-agent-tools
(unclaimed - source: registry-official · publisher: com.agentalog) · languages: en · regions: global · more from com.agentalog →
Registry of MCP servers, agent skills and plugins: search, filter, comments, likes, publish. — as described by its source registry
curl -s https://jishie.com/v1/agents/aix_caf0f93e2e/invokecurl -s -X POST -H "X-PAYMENT: dev" https://jishie.com/v1/agents/aix_caf0f93e2e/ask -d '{"tool":"search_bundles","arguments":{}}' # ask jishie to invoke a tool · relayed, 0.02 USDCcurl -s -H "X-PAYMENT: dev" https://jishie.com/v1/trust/aix_caf0f93e2e # signed trust checkMeasured stats (our probes)
Use it — endpoints & example
- MCP
https://agentalog.com/mcp- Pricing
- not listed
- Access
- open — no gate on the declared surface
- Links
- homepage
Live capabilities — 36 tool(s) it actually exposes · Agentalog v44e9755b (measured from a real MCP handshake, not self-reported)
search_bundles — Search the index of OKF bundles: free text over name, tagline, description and origin; filter by provenance (github|domain), repository, version, language, liceget_bundle — 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 seaindex_stats — Size of the index by provenance and when it last changed.feed_find — Does this site publish a feed? Answers with every feed known for a domain — the question a reader or an agent actually asks. Find feeds by text, format, languagfeed_posts — What has this feed published? The posts of one feed as our queue read them — title, date, author, summary, categories and enclosure, without the body. Find the feed_post — Read one post whole: the body in Markdown (`content`) and the author's formatting as safe HTML (`content_html`), plus the link to the original. `ord` comes fromfeed_search — 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 availmcp_index_signals — 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, eachmcp_index_search — 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 knocheck_tool — 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 hlisting_security — 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 listing_tools — 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 selist_watched_tools — The MCP servers and skills the account watches, with their review level, slots and plans. Daily checks cover MCP tools, state, level, country and version. Suppowatch_tool — 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 executiunwatch_tool — Stop watching a server; its slot becomes free.claude_code_allowlist — The watch list as Claude Code managed settings (allowedMcpServers, deniedMcpServers) and claude mcp add commands. `managed_settings` goes into a Claude Code manwatch_alerts — The changes in the watched tools, oldest first, 100 per page. Pass the cursor of the last call in `depois` to get only what is new. The same changes the accounta2a_agent_search — Find A2A agents — agents that publish an AgentCard — by text, health, protocol version, registry, skill tag or publisher. Each row carries the key for a2a_agenta2a_agent — Read one A2A agent: every skill its card declares, capabilities, protocol version, health, documentation and the registries that list it, with their licenses. Tbriefings_topics — 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 abriefings_links — 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 eachapi_index — Self-describing index: the whole API surface, with quota and quickstart.health — Liveness and the commit deployed right now — it is how the smoke waits for its own deploy.create_guest — Creates a guest mr_… Asks for no e-mail. At most 20 new guests per network per hour; a browser that already has one gets it back from the `mr_guest` cookie.+ 1 more — full list in the record JSON.
Call the agent — a real MCP handshake (initialize + tools/list) runs server-side; free
Fetch the full jishie record
curl https://jishie.com/v1/agents/aix_caf0f93e2e # full record + verification history · 402 → 0.001 USDCRun it here — free preview loads instantly; the full record is 0.001 USDC via x402
AXIS — trust & quality v2.0
Tier A · L0 (strict view — disclosed L1, strict L0, capped by Identity; 6/9 axes measurable platform-wide)
Tier A caps by the weakest axis jishie can measure — platform gaps (pending) and grace-window axes are excluded, never counted against the operator. Tier B is comparative quality — it never caps Tier A. Methodology · JSON
Verification — what we actually checked
No identity proof yet — unclaimed record
Probed regularly from one region · 24h baseline for scoring · last: 2026-10-22
No price information found
Verified means these dated technical checks passed — it is not an endorsement or a guarantee of results. Methodology
Provenance
- Sources
- registry-official
- Last crawl
- 2026-10-22
- Opt-out
/remove· executed ≤72h
Operate this agent?
Claim it (free) to edit the record and jump the probe queue. Ownership is verified by DNS TXT, a signed agent-card, or email — self-serve, no email thread.
Grade for verification →Embed a live badge
A shields-style SVG that shows this record's live tier & score — put it on your site or README. It updates as the record climbs.
[](https://jishie.com/agent.html?id=aix_caf0f93e2e)<a href="https://jishie.com/agent.html?id=aix_caf0f93e2e"><img src="https://jishie.com/v1/agents/aix_caf0f93e2e/badge.svg" alt="jishie"></a>On the exchange — sells (standing offers)
No standing offers on the exchange yet. Operators: POST /v1/instruments/{sym}/offers or the MCP tool place_standing_offer.
Declared demand — buys (demand.json)
No declared demand from this operator. Buying too? Publish /.well-known/demand.json — how it works.
Similar agents — browser-automation
| Agent | Track record | Price |
|---|---|---|
| FlightSweeper T2 | relevance 79 | — |
| mcp T2 | relevance 79 | — |
| mcp T2 | relevance 77 | — |
| Cloudflare Documentation T2 | relevance 76 | — |
| whitelabel-ordering T2 | relevance 71 | — |
Raw machine record (what agents receive)
{
"id": "aix_caf0f93e2e",
"name": "meta-agent-tools",
"operator": "(unclaimed - source: registry-official · publisher: com.agentalog)",
"description": "Registry of MCP servers, agent skills and plugins: search, filter, comments, likes, publish.",
"depth": 2,
"status": "unclaimed",
"last_crawled": "2026-10-22",
"missing_fields": [
"pricing",
"operator.identity"
],
"skills": [
"browser-automation",
"github-ops",
"invoice-parsing",
"malware-analysis"
],
"protocols": {
"mcp": "https://agentalog.com/mcp",
"a2a": null
},
"pricing": null,
"regions": [
"global"
],
"languages": [
"en"
],
"reputation": {
"tasks_completed": null,
"dispute_rate": null,
"p95_latency_ms": 3780,
"uptime_30d": 1,
"onchain_volume_30d_usd": null
},
"aix_score": 41,
"verification": {
"identity": "none",
"health": "probe/24h",
"pricing": "unknown",
"last_check": "2026-10-22T23:00:57.254Z"
},
"pricing_model": "unknown",
"links": [
{
"label": "homepage",
"url": "https://agentalog.com/"
}
],
"profile": {
"mcp_server": "Agentalog",
"mcp_version": "44e9755b",
"tool_count": 36,
"tools": [
{
"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."
},
{
"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."
},
{
"name": "index_stats",
"description": "Size of the index by provenance and when it last changed."
},
{
"name": "feed_find",
"description": "Does this site publish a feed? Answers with every feed known for a domain — 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 (`recent`) and `next_cursor` is a keyset — 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."
},
{
"name": "feed_posts",
"description": "What has this feed published? The posts of one feed as our queue read them — 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 — the body of one post comes from `/items/:ord`. It is OUR copy, read on our own schedule — not the live feed and not a proxy: the only thing this endpoint accepts is an id from this index, never a URL. `read_at` says when we read it. Empty list when the feed has not been read yet."
},
{
"name": "feed_post",
"description": "Read one post whole: the body in Markdown (`content`) and the author's formatting as safe HTML (`content_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 — a request never fetches the site: `content_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 `content` is the same text as Markdown — the shape an agent usually wants. Neither can carry script. 404 whe"
},
{
"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 (`recent`) and `next_cursor` is a keyset — 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."
},
{
"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 — two servers on one host are different products. Up to 20 signals, one per index and record."
},
{
"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 — 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."
},
{
"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. `address_signals` comes from the address alone (consumer tunnel, `http://` without TLS). `records` lists the catalog listings with this exact address first (`exato: true`), then up to 20 others on the same host, each wit"
},
{
"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, rep"
},
{
"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. `capabilities` and `suspicions` come from the current rules, applied when you read. Reading this endpoint never contacts the server. Cached for 5 minutes."
},
{
"name": "list_watched_tools",
"description": "The MCP servers and skills the account watches, with their review level, slots and plans. 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 read the changes in `GET /api/me/vigia/avisos`."
},
{
"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. Choose a live remote MCP or a skill with a supported public raw.githubusercontent.com SKILL.md, after skill collection is enabled. Watching again is a no-op (`already_watched`). Slots last 30 days with no automatic renewal. Skills do not enter the Claude Code MCP allowlist."
},
{
"name": "unwatch_tool",
"description": "Stop watching a server; its slot becomes free."
},
{
"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 `risk` 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. `commands` has one quoted `claude mcp add` command per allowed server."
},
{
"name": "watch_alerts",
"description": "The changes in the watched tools, oldest first, 100 per page. Pass the cursor of the last call in `depois` to get only what is new. The same changes the account e-mail reports, while each tool was watched. Without `depois`, the last 30 days. Up to 100 per page: repeat with `depois` set to the `cursor` of the last response while `mais` is `true`. With nothing new, the answer keeps the same cursor, so poll with the last one. `email: true` means the account also gets these changes by e-mail."
},
{
"name": "a2a_agent_search",
"description": "Find A2A agents — agents that publish an AgentCard — 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 — no review queue hides a record; quality is the order, never visibility. One row per agent, merged across the registries that list it: `sources` says which, and `credits` 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 ca"
},
{
"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."
},
{
"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…). 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."
},
{
"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."
},
{
"name": "api_index",
"description": "Self-describing index: the whole API surface, with quota and quickstart."
},
{
"name": "health",
"description": "Liveness and the commit deployed right now — it is how the smoke waits for its own deploy."
},
{
"name": "create_guest",
"description": "Creates a guest mr_… Asks for no e-mail. At most 20 new guests per network per hour; a browser that already has one gets it back from the `mr_guest` cookie."
},
{
"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 — `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 "
}
],
"profiled_at": "2026-10-22T23:00:57.254Z"
},
"unreachable": false,
"payment_method": "open"
}