minmap-app
https://mindmap-mcp-directory.keenethics-labs.com
Registry code: 8e7e3629ac92ca5c
Turn outlines and hierarchical notes into interactive mind maps through a hosted remote MCP server.
from a public catalogue that lists it, not from the operator
- endpoint
- https://mindmap-mcp-directory.keenethics-labs.com/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is minmap-app live?
- Yes — it answered the hub's last check (checked 5h ago). It answered 99% of checks over the last 30 days.
- Is minmap-app free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does minmap-app have?
- 1 tool: render_mindmap.
- Is minmap-app safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99%· all time 99%
last good check
of 1 tools
- degraded → live
- live → degraded· HTTP 500
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- render an outline as a mind map
- takes → gives
- text → images
- tools
- 1 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
render_mindmap reads unknown 26h ago
Render an interactive MCP app mind map when the user needs hierarchical structure shown visually instead of as prose. Use it for breaking down ideas, plans, study material, or systems into a root topic with nested branches; do not use it for tables, flowcharts, Mermaid/Graphviz diagrams, or plain text lists. Input `mindmap_markdown` must be a clean markdown tree with one `#` root heading and 2-space-indented bullet nesting. If the user gives prose, first reshape it into that hierarchy, then call this tool.
{ "type": "object", "required": [ "mindmap_markdown" ], "properties": { "title": { "type": "string", "description": "Optional short title for the mind map" }, "mindmap_markdown": { "type": "string", "description": "Markdown tree for a mind map. Preferred structure: one top-level heading for the root topic, then nested bullet points for branches and leaves using consistent 2-space indentation. Example: `# Product Launch Strategy\n\n- Marketing\n - Social Media\n - Twitter\n - LinkedIn\n - Email Campaign\n - Newsletter\n - Promo Codes\n- Engineering\n - QA Testing\n - Server Scaling\n - Final Deployment\n- Customer Support\n - Help Docs Updated\n - Support Training`. When the topic is suitable for emojis (e.g., marketing, events, social media, holidays, categories like food/travel), use relevant emojis in node names to make the diagram more appealing — like 📱 for Social Media or 🚀 for Launch. Avoid prose paragraphs, tables, fenced code blocks, and mixed list styles." } } }arguments 16 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id8e7e3629ac92ca5c.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/8e7e3629ac92ca5c/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/8e7e3629ac92ca5c?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.
- mental-tests-mcp-app.keenethics-labs.com Mental Health Tests