NoInfra MCP server
ai.noinfra/noinfra-mcpnoinfra.aistreamable-httpv0.2.0Scanned
Discover managed business agents. Private capabilities require owner authorization and eligibility.
4 tools: 2 change things and 2 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 0
- 1 finding
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 NoInfra MCP server can do
The NoInfra MCP server is published by noinfra.ai, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: noinfra.recommend_agent and noinfra.email.provision), but cannot delete data. 2 tools only read.
1 tool reads private data (noinfra.email.provision); 1 tool brings in text other people can write (noinfra.email.provision).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 9, 2026, version 0.2.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.
4 tools
Changes things 2Claude Code: ask
noinfra.email.provisionGet a dedicated NoInfra email inbox for an agent running anywhere.Reads private dataReads text others write1 finding
Why it is in this group
- The description's first verb is "get": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- private-dataThe name "noinfra.email.provision" says "email": it reads mail.
- private-dataThe description's first sentence says "get" and "email": it reads mail.
- untrusted-inputThe name "noinfra.email.provision" says "email": it reads inbound email, which other people can write.
- untrusted-inputThe description's first sentence says "get" and "email": it reads inbound email, which other people can write.
Findings
- Warn
The server marks "noinfra.email.provision" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "get": a word for reading.
Description, as the server wrote it Get a dedicated NoInfra email inbox for an agent running anywhere. Your NoInfra account owner must authorize access first. Reuse the same idempotency key when retrying.
Annotations the server declares
- title: Get an agent email inbox
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
noinfra.recommend_agentRecommend a NoInfra hosted agent for a described workflow.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Recommend a NoInfra hosted agent for a described workflow.
Annotations the server declares
- title: Recommend NoInfra agent
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 2Show 2 read-only tools
noinfra.catalog.getReturn the public NoInfra hosted-agent catalog and product links.No findings
Why it is in this group
- The name "noinfra.catalog.get" says "get": a word for reading.
Description, as the server wrote it Return the public NoInfra hosted-agent catalog and product links.
Annotations the server declares
- title: Get NoInfra catalog
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
noinfra.services.listList NoInfra agent services and show which are available to the current caller.No findings
Why it is in this group
- The name "noinfra.services.list" says "list": a word for reading.
Description, as the server wrote it List NoInfra agent services and show which are available to the current caller.
Annotations the server declares
- title: List NoInfra services
- 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 18, 2026, 16:23 UTC, unchanged since Oct 27, 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
- https://mcp.noinfra.ai/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://api.noinfra.ai
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- 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://mcp.noinfra.ai/mcp: tools/list returned 4 tools to an anonymous client, including noinfra.recommend_agent (write), noinfra.email.provision (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "noinfra.email.provision" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "get": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http noinfra https://mcp.noinfra.ai/mcpclaude mcp add --transport http noinfra https://mcp.noinfra.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__noinfra__noinfra_services_list",
"mcp__noinfra__noinfra_catalog_get"
],
"ask": [
"mcp__noinfra__noinfra_recommend_agent",
"mcp__noinfra__noinfra_email_provision"
],
"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 noinfra. Review it before you use it.
Capability tags behind 1 rule
- mcp__noinfra__noinfra_email_provision 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/ai.noinfra/noinfra-mcp/verify?hash=278a96dae079a7d2536a87a4e31228dbe02412bec0cc1be5264214bf7f437925" | jq -e '.changed == false'Pinned hash 278a96dae079, from Nov 9, 2026, 12:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.noinfra/noinfra-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.noinfra/noinfra-mcp)Source: MCP Registry. Synced Oct 26, 2026, 22:17 UTC.
NoInfra MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the NoInfra MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the NoInfra MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the NoInfra 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 NoInfra MCP server have?
- 4 tools: 2 write, 2 read. noinfra.recommend_agent, noinfra.email.provision, noinfra.services.list and noinfra.catalog.get.
Does the NoInfra MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the NoInfra MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the NoInfra MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 9, 2026.