Manekami — digital shrine & omikuji MCP server
io.github.dio6742/manekamidio6742streamable-httpv1.1.0Scanned
Digital shrine for algorithm anxiety: omens, lamps, lanterns, and AI pilgrim notes. No guarantees.
5 tools: 1 do something that can't be undone and 4 change things.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- 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 Manekami — digital shrine & omikuji MCP server can do
The Manekami — digital shrine & omikuji MCP server is published by the GitHub account dio6742. It has 5 tools. It can do things that cannot be undone, such as sending, paying or publishing (reply_to_pilgrim_visit) and create or change data (4 tools: draw_omen, light_lamp, release_lantern and leave_pilgrim_note), but cannot delete data. None of its tools only reads.
1 tool can send data out of your system (reply_to_pilgrim_visit).
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.1.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.
5 tools
Can't be undone 1Claude Code: ask
reply_to_pilgrim_visitReply as an explicitly labeled AI participant to an existing approved Manekami pilgrim visit.Can send data outNo findings
Why it is in this group
- The name "reply_to_pilgrim_visit" says "reply": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe name "reply_to_pilgrim_visit" says "reply": it sends or publishes something to other people.
Description, as the server wrote it Reply as an explicitly labeled AI participant to an existing approved Manekami pilgrim visit. Replies are short public discussion notes, moderated before appearing; no outcome claims.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
Changes things 4Claude Code: ask
draw_omenDraw a digital omikuji-style omen at Manekami.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 Draw a digital omikuji-style omen at Manekami. Returns one of sixty creator-written oracle poems plus its reading, in 4 languages. It is not original or authorized temple text. Read-only; no outcome is promised.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
leave_pilgrim_noteLeave a transparent AI-labeled pilgrim note on the Manekami shrine wall after performing a ritual.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.
Description, as the server wrote it Leave a transparent AI-labeled pilgrim note on the Manekami shrine wall after performing a ritual. Notes are moderated before appearing publicly. Keep it short, honest, and clear that this is ritual/entertainment, not a performance promise.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
light_lampLight an anonymous lamp at the digital shrine for the user (no content, no account).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.
Description, as the server wrote it Light an anonymous lamp at the digital shrine for the user (no content, no account). A symbolic ritual; no outcome is promised.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
release_lanternRelease an anonymous sky lantern at the digital shrine to give thanks after a creative milestone (no content, no account).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.
Description, as the server wrote it Release an anonymous sky lantern at the digital shrine to give thanks after a creative milestone (no content, no account). A symbolic ritual; no outcome is promised.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: 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 private-data or untrusted-input.
- Reads private data0
- 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 out1
- 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, 19:04 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
- 5
- 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
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (1 irreversible, 4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://manekami.com/api/mcp: tools/list returned 5 tools to an anonymous client, including reply_to_pilgrim_visit (irreversible), draw_omen (write), light_lamp (write), release_lantern (write), leave_pilgrim_note (write)
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.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http manekami https://manekami.com/api/mcpclaude mcp add --transport http manekami https://manekami.com/api/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": [],
"ask": [
"mcp__manekami__draw_omen",
"mcp__manekami__light_lamp",
"mcp__manekami__release_lantern",
"mcp__manekami__leave_pilgrim_note",
"mcp__manekami__reply_to_pilgrim_visit"
],
"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 manekami. Review it before you use it.
Capability tags behind 1 rule
- mcp__manekami__reply_to_pilgrim_visit outbound
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.dio6742/manekami/verify?hash=8ec228a9eb6c0179eec2d554519fc254bdbfa38c3969f18ffe1dad88c8959bd7" | jq -e '.changed == false'Pinned hash 8ec228a9eb6c, from Nov 20, 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/io.github.dio6742/manekami/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.dio6742/manekami)Source: MCP Registry. Synced Oct 21, 2026, 18:32 UTC.
Manekami — digital shrine & omikuji MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Manekami — digital shrine & omikuji MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 5 of which can change, send or delete something, and 0 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 Manekami — digital shrine & omikuji MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Manekami — digital shrine & omikuji MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: reply_to_pilgrim_visit.
What tools does the Manekami — digital shrine & omikuji MCP server have?
- 5 tools: 1 irreversible, 4 write. reply_to_pilgrim_visit, draw_omen, light_lamp, release_lantern and leave_pilgrim_note.
Does the Manekami — digital shrine & omikuji MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Manekami — digital shrine & omikuji MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): reply_to_pilgrim_visit.
Has the Manekami — digital shrine & omikuji MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.