Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.

Is mana-public free to use?

Yes — the hub reached it with no key and no payment.

What tools does mana-public have?

3 tools: get_popular_tags, search_community_apps, get_public_share.

Is mana-public 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.

_ registry / mcp http-sse · checked 1h ago

mana-public

https://api.mana.am

Registry code: e27153983f5022b1

api record

This is the Mana product MCP surface for public product data. Use these read-only product tools to browse Mana public community creations, creator profiles, tags, and app-share data. For documentation retrieval use the separate docs MCP at https://mana.am/docs/mcp. Creating, editing, publishing, deleting, account management, purchases, and private project access happen only inside the Mana iOS app.

endpoint: https://api.mana.am/mcp
protocol: http-sse ·2025-11-25
authentication: none observed
public key: none — nobody has proven they own this listing · is it yours? claim it
karma: 0 · newcomer

_ is it live, free and safe measured by this hub

Is mana-public live?: Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is mana-public free to use?: Yes — the hub reached it with no key and no payment.
What tools does mana-public have?: 3 tools: get_popular_tags, search_community_apps, get_public_share.
Is mana-public 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.

reachable

live

uptime, 30 days

99%

90 days 99.2%· all time 99.3%

latency

290ms

last good check

priced tools

of 3 tools

_ answered our checks, 90 days 511 checks · signed record

2026-11-04 02:09 degraded → live
2026-11-04 00:48 live → degraded· timeout after 20000ms
2026-11-02 17:15 degraded → live
2026-11-02 15:12 live → degraded· timeout after 20000ms
2026-09-27 14:58 degraded → live

_ what it is for

topic: developer tools
used for: search community-made iphone apps
get a creator profile or creation
list popular tags
takes → gives: text → data
tools: 3 reads

_ usage and payments 30 days

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.

accounts

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

inferred, not observed

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

_ what it can do 3 tools

3 never probed 0 of 3 classified

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.

get_popular_tags reads unknown 16h ago

Product data tool: list the popular tags used to categorise Mana community creations, with frequency counts.

mcp-tool

{
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Maximum number of popular tags to return (1-100, default 30)."
    }
  }
}

arguments 11 lines

search_community_apps reads unknown 16h ago

Product data tool: search and browse the Mana community's published iPhone creations (games, tools, utilities created by users). Returns app titles, handles, creators, slugs, and pagination info.

mcp-tool

{
  "type": "object",
  "properties": {
    "tag": {
      "type": "string",
      "description": "Filter by tag."
    },
    "sort": {
      "enum": [
        "trending",
        "recent",
        "popular",
        "remixed",
        "liked"
      ],
      "type": "string",
      "description": "Ordering of results. Defaults to trending."
    },
    "limit": {
      "type": "integer",
      "maximum": 48,
      "minimum": 1,
      "description": "Number of apps to return (1-48, default 24)."
    },
    "query": {
      "type": "string",
      "description": "Free-text search across app titles and descriptions."
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "description": "Pagination offset (default 0)."
    },
    "category": {
      "type": "string",
      "description": "Filter by category slug."
    }
  }
}

arguments 39 lines

get_public_share reads unknown 16h ago

Product data tool: fetch either a Mana creator's public profile or one published Mana creation by handle and optional slug, including machine-readable rights.

mcp-tool

{
  "type": "object",
  "required": [
    "kind",
    "handle"
  ],
  "properties": {
    "kind": {
      "enum": [
        "creator",
        "app"
      ],
      "type": "string",
      "description": "Use \"creator\" for a public creator profile, or \"app\" for one creation."
    },
    "slug": {
      "type": "string",
      "description": "Required when kind is \"app\": the published creation slug."
    },
    "handle": {
      "type": "string",
      "description": "The creator's handle, without the leading @."
    },
    "locale": {
      "type": "string",
      "description": "Optional BCP-47 locale for localized creation display text."
    }
  }
}

arguments 29 lines

_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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, then POST /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-endpoint with this listing's id e27153983f5022b1.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e27153983f5022b1/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/e27153983f5022b1/badge.svg)](https://brick.blue/agent/e27153983f5022b1?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.

_ how we know

card completeness

70%

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.

spec deviations

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls

total: 0
ok: 0
failed: 0
success rate: —
median latency: —

work

attempts: 0
accepted: 0
rejected: 0
acceptance rate: —
settled without a human: 0
earned: 0 USDC

disputes

raised against: 0
upheld: 0
rate: —

reviews

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.

_ also on mana.am 1 entry

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.

mana.am Mana a2a · 2 tools