Skip to content

Find MCP - Agentage MCP Directory

io.agentage/find-mcpagentage.iostreamable-httpv1.13.6Scanned

Search the official MCP registry: 17,000+ servers with trust grades, stars, tools, install config.

3 tools: 3 only read.

Tools: 0 delete, 0 irreversible, 0 write, 3 read.
  • Reads private data · 3
  • Reads text others write · 3
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Find MCP - Agentage MCP Directory can do

The Find MCP - Agentage MCP Directory is published by agentage.io, a domain the MCP Registry verified. It has 3 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

3 tools read private data (mcp_search, mcp_get and mcp_categories); 3 tools bring in text other people can write (mcp_search, mcp_get and mcp_categories).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 1.13.6.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Only reads 3Show 3 read-only tools
  • mcp_categoriesList the directory's available filter values - every category, language, and license, each with how many servers carry it.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "directory": it reads files.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    List the directory's available filter values - every category, language, and license, each with how many servers carry it. Call this BEFORE mcp_search when you intend to filter, so you pass exact, existing values for the type/category/language/license arguments instead of guessing. Takes no input. Read-only.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • mcp_getFetch the complete record for ONE MCP server in the agentage directory by its canonical slug: full description, categories, the packages and remote endpoints it ships, the tools it…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "mcp_get" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "fetch" and "directory": it reads files.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Fetch the complete record for ONE MCP server in the agentage directory by its canonical slug: full description, categories, the packages and remote endpoints it ships, the tools it exposes, a ready-to-run install command, and a README excerpt. Use this after mcp_search to get the depth a result card omits - pass a slug exactly as returned by mcp_search. Slugs are canonical and registry-derived ("io-github-github-github-mcp-server"), NOT the plain product name ("github"); if you pass a plain name anyway it is resolved by search as a fallback - a single confident match returns that server (with `resolved_from` set), anything else returns an error naming the candidate slugs to retry with. No slug yet? call mcp_search first. Read-only.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:55 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Posture changes

  1. Oct 29, 2026
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 200
    • tools/list served without credentials: no to yes
    • Protocol version: none to 2025-06-18

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: no -> yes; HTTP status of an anonymous initialize: none -> 200; tools/list served without credentials: no -> yes (and 1 more).View diff
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 200
    • tools/list served without credentials: no to yes
    • Protocol version: none to 2025-06-18

Install

Pinned to version 1.13.6. Values in angle brackets are yours to fill in.

claude mcp add --transport http find https://catalog.agentage.io/mcp
claude mcp add --transport http find https://catalog.agentage.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__find__mcp_search",
      "mcp__find__mcp_get",
      "mcp__find__mcp_categories"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as find. Review it before you use it.

Capability tags behind 3 rules
  • mcp__find__mcp_search private-data, untrusted-input
  • mcp__find__mcp_get private-data, untrusted-input
  • mcp__find__mcp_categories private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.agentage/find-mcp/verify?hash=7a61a9d7430f6a5514c50976428db7132792403e27e313305d7af185e413efe4" | jq -e '.changed == false'

Pinned hash 7a61a9d7430f, from Nov 21, 2026, 04:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.agentage/find-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.agentage/find-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.agentage/find-mcp.svg)](https://radar.anlyon.com/servers/io.agentage/find-mcp)

Source: MCP Registry. Synced Nov 21, 2026, 04:17 UTC.

Find MCP - Agentage MCP Directory: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Find MCP - Agentage MCP Directory safe?

No scan can promise that. What its definitions show: 3 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the Find MCP - Agentage MCP Directory delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Find MCP - Agentage MCP Directory do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Find MCP - Agentage MCP Directory have?

3 tools: 3 read. mcp_search, mcp_get and mcp_categories.

Does the Find MCP - Agentage MCP Directory need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Find MCP - Agentage MCP Directory send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Find MCP - Agentage MCP Directory changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.