Amito — Interface specifications MCP server
io.github.jarvinmito/amitojarvinmitostreamable-httpv1.0.0Scanned
Interface requirements, missing-decision checks, and public frontend portfolio information.
3 tools: 3 only read.
- Reads private data · 2
- Reads text others write · 0
- 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.
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 Amito — Interface specifications MCP server can do
The Amito — Interface specifications MCP server is published by the GitHub account jarvinmito. It has 3 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
2 tools read private data (search and fetch).
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 20, 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
Only reads 3Show 3 read-only tools
fetchRead an exact document ID returned by search, such as spec:form or project:dupe.Reads private dataNo findings
Why it is in this group
- The name "fetch" says "fetch": a word for reading.
What it can reach
- private-dataThe description's first sentence says "read" and "document": it reads documents.
Description, as the server wrote it Read an exact document ID returned by search, such as spec:form or project:dupe. Returns the full document, canonical source URL, and revision metadata. Does not fetch arbitrary URLs or files.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
searchFind interface specifications for forms, tables, onboarding, and dashboards, or public facts about Jan Arvin Mito's projects and current Dupe contract.Reads private dataNo findings
Why it is in this group
- The name "search" says "search": a word for reading.
What it can reach
- private-dataThe description's first sentence says "find" and "table": it reads databases.
Description, as the server wrote it Find interface specifications for forms, tables, onboarding, and dashboards, or public facts about Jan Arvin Mito's projects and current Dupe contract. Returns document IDs and source URLs; use fetch for complete content.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
validate_design_specCheck whether a draft supplies the required decisions for form, table, onboarding, or dashboard.No findings
Why it is in this group
- The name "validate_design_spec" says "validate": a word for reading.
Description, as the server wrote it Check whether a draft supplies the required decisions for form, table, onboarding, or dashboard. First fetch spec:<pattern> for the exact decision keys. Each decisions value describes the intended behavior; explain why if a requirement does not apply. Returns missing or placeholder decisions and acceptance scenarios. Does not inspect code, certify accessibility, or save the submitted draft.
Annotations the server declares
- 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 untrusted-input or outbound.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- 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 21, 2026, 19:22 UTC, unchanged since Nov 7, 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
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.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http amito https://amito.dev/mcpclaude mcp add --transport http amito https://amito.dev/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__amito__search",
"mcp__amito__fetch",
"mcp__amito__validate_design_spec"
],
"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 amito. Review it before you use it.
Capability tags behind 2 rules
- mcp__amito__search private-data
- mcp__amito__fetch private-data
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.github.jarvinmito/amito/verify?hash=e73ebc2aee6b64862f1cba9042a223932e1ccd5b5756ec6102a40a93dadd965e" | jq -e '.changed == false'Pinned hash e73ebc2aee6b, from Nov 20, 2026, 13:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.jarvinmito/amito/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.jarvinmito/amito)Source: MCP Registry. Synced Nov 6, 2026, 12:17 UTC.
Amito — Interface specifications MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Amito — Interface specifications MCP server 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 Amito — Interface specifications MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Amito — Interface specifications 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 Amito — Interface specifications MCP server have?
- 3 tools: 3 read. search, fetch and validate_design_spec.
Does the Amito — Interface specifications MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Amito — Interface specifications MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Amito — Interface specifications MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.