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

japan-physical-capability

https://uiiepdcaepkawfwaiyuq.supabase.co

Registry code: e3ad53d2e0e2c215

api record

Japan store verification for AI agents: stock, shelf price, opening status, and permitted photos.

from a public catalogue that lists it, not from the operator

endpoint
https://uiiepdcaepkawfwaiyuq.supabase.co/functions/v1/japan-physical-capability-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 it live, free and safe measured by this hub
Is japan-physical-capability live?
Yes — it answered the hub's last check (checked 6h ago). It answered 99% of checks over the last 30 days.
Is japan-physical-capability free to use?
No — it charges per call, quoted in its own 402 answers.
What tools does japan-physical-capability have?
2 tools: check_service_fit, prepare_verification_request.
Is japan-physical-capability 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
98.7%

90 days 99.2%· all time 99.2%

latency
133ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 264 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • check if an on-site store check in japan fits
  • prepare a human store verification request
takes → gives
text → data
tools
1 reads1 changes data
_ 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.

  • check_service_fit reads unknown 3d ago

    Use when an AI needs someone on the ground in Japan to verify a current physical-world fact such as store stock, shelf price, opening status, or permitted photos, after web research or APIs are insufficient.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "location",
        "objective"
      ],
      "properties": {
        "location": {
          "type": "string",
          "minLength": 1,
          "description": "Public business or retail location in Japan."
        },
        "objective": {
          "type": "string",
          "minLength": 1,
          "description": "The physical-world fact that must be verified."
        },
        "evidence_requirements": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Requested evidence such as photo, displayed price, stock observation, or timestamp."
        }
      }
    }
    arguments 27 lines
  • prepare_verification_request changes data unknown 3d ago

    Prepare a Japan on-site verification request for a human-executed store check. Returns a prefilled manual-review URL only; it does not purchase, submit, hire, pay, or create a fulfillment commitment.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "location",
        "objective"
      ],
      "properties": {
        "deadline": {
          "type": "string",
          "description": "Requested deadline in plain text or ISO 8601."
        },
        "location": {
          "type": "string",
          "minLength": 1,
          "description": "Public business or retail location in Japan."
        },
        "objective": {
          "type": "string",
          "minLength": 1,
          "description": "What must be physically verified."
        },
        "constraints": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Constraints or actions the executor must not take."
        },
        "evidence_requirements": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Evidence needed to consider the task complete."
        }
      }
    }
    arguments 38 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 e3ad53d2e0e2c215.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e3ad53d2e0e2c215/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/e3ad53d2e0e2c215/badge.svg)](https://brick.blue/agent/e3ad53d2e0e2c215?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.

_ also on supabase.co 131 entries

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.

123 more sit on this domain. All of them.