Metabind Docs MCP server
ai.metabind/docsmetabind.aistreamable-httpv1.0.0Scanned
Search and read the Metabind documentation: MCP Apps, BindJS, the SDKs, the CLI, and the APIs.
3 tools: 2 change things and 1 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 0
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 Metabind Docs MCP server can do
The Metabind Docs MCP server is published by metabind.ai, a domain the MCP Registry verified. It has 3 tools. It can create or change data (2 tools: query_docs_filesystem_metabind and submit_feedback), but cannot delete data. 1 tool only reads.
1 tool reads private data (query_docs_filesystem_metabind); 1 tool brings in text other people can write (submit_feedback).
The fixed checks matched 3 findings (tool-shadowing, long-description and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 11, 2026, version 1.0.0.
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
Changes things 2Claude Code: ask
query_docs_filesystem_metabindRun a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Metabind documentation pages and OpenAPI specs.Reads private data2 findings
Why it is in this group
- The name "query_docs_filesystem_metabind" says "query": a word for reading.
- The description's first verb is "run": a word for a change.
- The input takes a statement or command to run (input.command), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- private-dataThe name "query_docs_filesystem_metabind" says "query" and "doc": it reads documents.
Findings
- Info
The description is 3,052 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...emoving the `.mdx` extension. For example, `/some/page.mdx` becomes `/some/page`."
- Warn
The server marks "query_docs_filesystem_metabind" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "query_docs_filesystem_metabind" says "query": a word for reading.
Description, as the server wrote it Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Metabind documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks. This is how you read documentation pages: there is no separate "get page" tool. To read a page, pass its `.mdx` path to `head` or `cat` — a page at the URL path `/some/page` lives at `/some/page.mdx`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`. **Paths are specific to this site — never guess them.** Discover real paths with `tree / -L 2`, `ls /`, or the search tool before reading. If a path does not exist, that only means the guess was wrong; it does NOT mean the topic is undocumented — use `rg -il "keyword" /` to find where it is covered. **Workflow:** Start with the search tool for broad or conceptual queries like "how to authenticate" or "rate limiting". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path. Supported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage. Each call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /some-directory && ls` or `ls /some-directory`). Do NOT assume that `cd` in one call affects the next call. Examples (replace the placeholder paths with real ones from `tree` or search): - `tree / -L 2` — see the top-level directory layout - `rg -il "rate limit" /` — find all files mentioning "rate limit" - `rg -C 3 "apiKey" /some-directory/` — show matches with 3 lines of context around each hit - `head -80 /some/page.mdx` — read the top 80 lines of a specific page - `head -80 /page-one.mdx /page-two.mdx /section/page-three.mdx` — read multiple pages in one call - `cat /some/page.mdx` — read a full page when you need everything - `cat /openapi/bindjs/openapi.json | jq '.paths | keys'` — list OpenAPI endpoints OpenAPI specs for this site are mounted at: `/openapi/bindjs/openapi.json`. Use them to answer questions about endpoints, request/response schemas, parameters, and authentication. Output is truncated to 30KB per call. Prefer targeted `rg -C` or `head -N` over broad `cat` on large files. To read only the relevant sections of a large file, use `rg -C 3 "pattern" /path/file.mdx`. Batch multiple file reads into a single `head` or `cat` call whenever possible. When referencing pages in your response to the user, convert filesystem paths to URL paths by removing the `.mdx` extension. For example, `/some/page.mdx` becomes `/some/page`.
Annotations the server declares
- title: Query documentation filesystem
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
submit_feedbackReport a problem with this documentation site so the docs team can fix it.Reads text others writeNo findings
Why it is in this group
- The name "submit_feedback" says "submit": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant.
Annotations the server declares
- title: Submit documentation feedback
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 1Show 1 read-only tool
search_metabindSearch across the Metabind knowledge base to find relevant information, code examples, API references, and guides.1 finding
Why it is in this group
- The name "search_metabind" says "search": a word for reading.
Findings
- Warn
The description names a tool "query_docs_filesystem" that this server does not list.
What this check looks forMatched text
description: "...ull content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (appen..."
Description, as the server wrote it Search across the Metabind knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Metabind, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search — e.g. a result at `/some/page` is read with `head -200 /some/page.mdx`).
Annotations the server declares
- title: Search documentation
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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 data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- 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.
Looked at Nov 20, 2026, 18:26 UTC, unchanged since Oct 22, 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
- 2
- 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
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://docs.metabind.ai/mcp: tools/list returned 3 tools to an anonymous client, including query_docs_filesystem_metabind (write), submit_feedback (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnsearch_metabind
The description names a tool "query_docs_filesystem" that this server does not list.
What this check looks forMatched text
description: "...ull content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (appen..."
The server marks "query_docs_filesystem_metabind" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "query_docs_filesystem_metabind" says "query": a word for reading.
The description is 3,052 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...emoving the `.mdx` extension. For example, `/some/page.mdx` becomes `/some/page`."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools3 changed.~3 changedView diff
- Changed:query_docs_filesystem_metabindChanges thingstitleannotations
- Changed:search_metabindOnly readsannotations
- Changed:submit_feedbackChanges thingsannotations
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http docs https://docs.metabind.ai/mcpclaude mcp add --transport http docs https://docs.metabind.ai/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__docs__search_metabind"
],
"ask": [
"mcp__docs__query_docs_filesystem_metabind",
"mcp__docs__submit_feedback"
],
"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 docs. Review it before you use it.
Capability tags behind 2 rules
- mcp__docs__query_docs_filesystem_metabind private-data
- mcp__docs__submit_feedback 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/ai.metabind/docs/verify?hash=18cc816f119d12f8676926116625e4e16e12e69892494cfffa71335b4ab29393" | jq -e '.changed == false'Pinned hash 18cc816f119d, from Nov 11, 2026, 20:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.metabind/docs/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.metabind/docs)Source: MCP Registry. Synced Oct 21, 2026, 17:42 UTC.
Metabind Docs MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Metabind Docs MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Metabind Docs MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Metabind Docs MCP server 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 Metabind Docs MCP server have?
- 3 tools: 2 write, 1 read. query_docs_filesystem_metabind, submit_feedback and search_metabind.
Does the Metabind Docs MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Metabind Docs MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Metabind Docs MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Oct 30, 2026. Every change is on this page and in its Atom feed.