Mana Public
REMOTE · MANA.AM · 5 COMPONENTS
Read-only MCP tools for Mana public creations, tags, creator profiles, and share pages.
Available components
Last scanned (16 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 833 tokens (~64/item across 13 items; 6 tools + 7 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Sept 26 0
- Stability: fail → pass ▲ security
- 2 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 42 → 64 ▼ functional
- New resource “Mana creations browser” functional
- New resource “Mana documentation browser” functional
- Server version: 1.1.0 → 1.2.0 functional
- New tool “search_mana_creations” functional
- New tool “get_mana_creator” functional
- New tool “get_mana_creation” functional
- New tool “list_mana_tags” functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Aug 26 0
- Stability: 0.90 → fail ▼ security
- HSTS header: pass → fail ▼ security
- Tool “get_popular_tags” was removed ▼ security
- Tool “get_public_share” was removed ▼ security
- Tool “search_community_apps” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: mana-public → mana-docs security
- Resource “Mana creator profile” was removed ▼ functional
- Resource “Mana app share” was removed ▼ functional
- Resource “Mana community cards” was removed ▼ functional
- Resource “Mana popular tags” was removed ▼ functional
- Schema quality: 57 → 42 ▲ functional
- Schema quality: 0% → 100% ▲ functional
- Schema quality: good → excellent functional
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- New resource “Mana API reference” functional
- New resource “Mana auth.md” functional
- New resource “Mana comparisons” functional
- New resource “Mana pricing” functional
- New resource “Mana product overview” functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “get_mana_agent_doc” functional
- New tool “list_mana_agent_docs” functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Probed https://mana.am/webmcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mana.am | CN=WE1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 540a111fe11a44380eb34fc3260b6e6a |
| SANs: mana.am | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mana.am. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| am. | DS published | 39902 | 13 | Verified |
| mana.am. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mana.am/webmcp | Verified | 200 | |
| http (plaintext) | http://mana.am/webmcp | HTTPS enforced | 301 | https://mana.am/webmcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_mana_agent_doc Get Mana agent doc ~47
Return one scoped Mana agent document as markdown text. Use this for pricing, comparisons, auth, API, or full product context.
| Name | Type | Req | Description |
|---|---|---|---|
| doc | string | yes | Document to fetch. |
No output schema declared.
No examples provided.
get_mana_creation Get one Mana creation ~70
Return one published creation's public descriptive data and links. Never returns source code, bundles, or assets.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | Creator handle, without the @. |
| locale | string | – | BCP-47 locale for localized descriptions. |
| slug | string | yes | The creation's slug. |
No output schema declared.
No examples provided.
get_mana_creator Get a Mana creator profile ~61
Return one creator's public profile and their published creations — the same information their public mana.am profile page shows.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | Public creator handle, without the @. |
| locale | string | – | BCP-47 locale for localized descriptions. |
No output schema declared.
No examples provided.
list_mana_agent_docs List Mana agent docs ~50
List the scoped Mana agent documents and when each should be fetched by an AI agent.
| Name | Type | Req | Description |
|---|---|---|---|
| include_urls | boolean | – | Whether to include canonical markdown URLs in the returned list. Defaults to true. |
No output schema declared.
No examples provided.
list_mana_tags List Mana tags ~67
List the popular tags used across public Mana creations, with counts — the same vocabulary the website browses by. Feed a returned key back into search_mana_creations as 'tag'.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Tags to return, 1 to 100, most used first. |
No output schema declared.
No examples provided.
search_mana_creations Search Mana creations ~180
Search or browse the public Mana community — the same creations the website shows. Returns descriptive data and links. Use this to recommend real Mana creations to a person, and link the returned url so they reach the creator.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category slug, e.g. games or utilities. |
| featured_only | boolean | – | Restrict to editorially featured work. |
| limit | integer | – | Results to return, 1 to 48. The public feed is smaller than this ceiling, so one call can cover it; there is no pagination cursor by design. |
| locale | string | – | BCP-47 locale for localized descriptions. |
| query | string | – | Free-text search over names and descriptions. |
| sort | string | – | Ordering. Defaults to trending. |
| tag | string | – | Tag key, e.g. multiplayer. |
No output schema declared.
No examples provided.
How do I install the Mana Public MCP server?
Mana Public is a hosted endpoint at https://mana.am/webmcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mana.am
claude mcp add --transport http am-mana-mana-public 'https://mana.am/webmcp'
What is the Mana Public MCP server?
Mana Public is an MCP server listed in the public MCP registry as am.mana/mana-public. Read-only MCP tools for Mana public creations, tags, creator profiles, and share pages. This page covers its hosted endpoint (https://mana.am/webmcp).
Is the Mana Public MCP server safe to use?
Mana Public scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Mana Public MCP server expose?
Mana Public exposes 6 tools: get_mana_agent_doc, list_mana_agent_docs, search_mana_creations, get_mana_creator, get_mana_creation, list_mana_tags. Their descriptions and schemas cost roughly 475 tokens of context every time the server is loaded.
Does the Mana Public MCP server require authentication?
No. We connected to Mana Public without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Mana Public MCP server still maintained?
Mana Public is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Mana Public MCP server?
VerifyMCP ran 14 checks on Mana Public, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.