Is zeroparadesdb live?

Yes — it answered the hub's last check (checked 49m ago). It answered 100% of checks over the last 30 days.

Is zeroparadesdb free to use?

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

What tools does zeroparadesdb have?

5 tools: lookup, get_record, list_entities, search, planner_link.

Is zeroparadesdb 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 streamable-http · checked 49m ago

zeroparadesdb

https://zeroparadesdb.com

Registry code: 9e5f84b4d6c9d603

api record

endpoint: https://zeroparadesdb.com/api/mcp
protocol: streamable-http ·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 it live, free and safe measured by this hub

Is zeroparadesdb live?: Yes — it answered the hub's last check (checked 49m ago). It answered 100% of checks over the last 30 days.
Is zeroparadesdb free to use?: Yes — the hub reached it with no key and no payment.
What tools does zeroparadesdb have?: 5 tools: lookup, get_record, list_entities, search, planner_link.
Is zeroparadesdb 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

100%

90 days 100%· all time 100%

latency

116ms

last good check

priced tools

of 5 tools

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

2026-10-24 08:04 unknown → live

_ 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

_ what it can do 5 tools

1 open 4 never probed 1 of 5 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.

planner_link open 49m ago

The site's planner prefilled with thoughts and a focus skill, after validating their ids. Thought phases are reinforced, unconditioned, suppressed or dissonant. Unknown ids are tool errors. This returns a link; it does not change a saved build.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "skill": {
      "type": "string"
    },
    "locale": {
      "enum": [
        "en",
        "es-419",
        "de",
        "ru",
        "zh-cn"
      ],
      "type": "string"
    },
    "thoughts": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "id"
        ],
        "properties": {
          "id": {
            "type": "string"
          },
          "phase": {
            "enum": [
              "reinforced",
              "unconditioned",
              "suppressed",
              "dissonant"
            ],
            "type": "string"
          }
        }
      }
    }
  }
}

arguments 42 lines

lookup unknown never probed

The best-matching records for a named skill, thought, item, character, task or place, with canonical page slugs, URLs and preview facts. Use search for dialogue passages. A missing term is a tool error with a search suggestion.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "term"
  ],
  "properties": {
    "term": {
      "type": "string"
    },
    "locale": {
      "enum": [
        "en",
        "es-419",
        "de",
        "ru",
        "zh-cn"
      ],
      "type": "string"
    }
  }
}

arguments 22 lines

get_record unknown 49m ago

One record by kind and stable id from search or lookup. Returns raw game fields, localized page projection and preview facts, plus canonical page slug and URL. A null page means no published page in that language. Missing ids are tool errors; use search rather than guessing ids from slugs.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "kind",
    "id"
  ],
  "properties": {
    "id": {
      "type": "string"
    },
    "kind": {
      "enum": [
        "skill",
        "item",
        "character",
        "task",
        "thought",
        "status-effect",
        "achievement",
        "persona",
        "progression-unit",
        "district",
        "waypoint",
        "location",
        "interior-location",
        "lore"
      ],
      "type": "string"
    },
    "locale": {
      "enum": [
        "en",
        "es-419",
        "de",
        "ru",
        "zh-cn"
      ],
      "type": "string"
    }
  }
}

arguments 42 lines

list_entities unknown 49m ago

Published page projections for one record kind and language, 50 per page. Null-page records are excluded rather than given invented links. Continue with nextPage; an out-of-range page is a tool error.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "kind"
  ],
  "properties": {
    "kind": {
      "enum": [
        "skill",
        "item",
        "character",
        "task",
        "thought",
        "status-effect",
        "achievement",
        "persona",
        "progression-unit",
        "district",
        "waypoint",
        "location",
        "interior-location",
        "lore"
      ],
      "type": "string"
    },
    "page": {
      "type": "number",
      "default": 1
    },
    "locale": {
      "enum": [
        "en",
        "es-419",
        "de",
        "ru",
        "zh-cn"
      ],
      "type": "string"
    }
  }
}

arguments 42 lines

search unknown never probed

The site's search over records, checks and dialogue, 50 results per page. Results include name, kind, stable id, canonical page slug and production URL. Checks include difficulty; passage URLs retain their fragment. Use page 2 and later up to pages to continue.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "kind": {
      "type": "string"
    },
    "page": {
      "type": "number"
    },
    "query": {
      "type": "string"
    },
    "locale": {
      "enum": [
        "en",
        "es-419",
        "de",
        "ru",
        "zh-cn"
      ],
      "type": "string"
    }
  }
}

arguments 28 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 9e5f84b4d6c9d603.

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

_ for your README measured, not declared

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

90%

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.