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

ai.migurei.pw/parallel-world

https://pw.migurei.ai

Registry code: a75e53681ecb1456

api record

Two read-only tools. check_ai_bot_access {"domain":"example.com"}: reads that site's public robots.txt (one request, nothing else) and says which AI bots of our registry are allowed or disallowed for "/", with the deciding rule; the domain is not stored. get_site_info {"topic":"all"} (or one of overview, pricing, scanner, contact, company, all): the same facts as the pages of https://pw.migurei.ai.

endpoint
https://pw.migurei.ai/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 ai.migurei.pw/parallel-world live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is ai.migurei.pw/parallel-world free to use?
Not measured yet.
What tools does ai.migurei.pw/parallel-world have?
2 tools: get_site_info, check_ai_bot_access.
Is ai.migurei.pw/parallel-world 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
159ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 1 checks · signed record
  • 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
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 2 tools
2 never probed 0 of 2 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_site_info unknown never probed

    Returns the facts published on this website, in Japanese: service overview, plans, prices and payment terms, how the scanner behaves, how to contact us, and the operating company. Each fact comes with the URL of the page that shows it. Read-only; it returns nothing that is not on the pages.

    mcp-tool

    {
      "type": "object",
      "required": [
        "topic"
      ],
      "properties": {
        "topic": {
          "enum": [
            "overview",
            "pricing",
            "scanner",
            "contact",
            "company",
            "all"
          ],
          "type": "string",
          "description": "Which facts to return"
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
  • check_ai_bot_access unknown never probed

    Reads the public robots.txt of a website (one request to https://<host>/robots.txt, nothing else on the site) and says, for each AI crawler and AI agent of the migurei bot registry (training crawlers such as GPTBot and ClaudeBot, search bots, fetchers that act for a user, and others), whether that bot is allowed or disallowed for the path "/", which robots.txt rule decided it, and whether the file exists. Input is a domain or URL; only public domain names are accepted (no IP addresses, no ports, no private hosts). Read-only; the domain is not stored. robots.txt is a request to bots, not access control, and a User-Agent is only a claim.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "type": "string",
          "maxLength": 300,
          "description": "A public domain name or a URL, for example example.com or https://example.com/page. Only its host is used."
        }
      },
      "additionalProperties": false
    }
    arguments 14 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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id a75e53681ecb1456.

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

_ for your README measured, not declared

measured by brick.blue

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

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
0

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.