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

lookthrough

https://app.lookthrough.workers.dev

Registry code: 7bad0d1ab9719dda

api record

Free check first (check_coverage), then create_order for x402 payment requirements, then get_report. Reports are best-effort research from public sources, not a compliance certificate.

endpoint
https://app.lookthrough.workers.dev/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 lookthrough live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is lookthrough free to use?
Yes — the hub reached it with no key and no payment.
What tools does lookthrough have?
3 tools: get_report, check_coverage, create_order.
Is lookthrough 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
152ms

last good check

priced tools
0

of 3 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

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_report unknown 2h ago

    Returns the status of an order and, once delivered, the report (structured JSON and plain text). Status values: pending_entity, pending_payment, paid, delivered. An unpaid order returns its payment requirements.

    mcp-tool

    {
      "type": "object",
      "required": [
        "order_id"
      ],
      "properties": {
        "order_id": {
          "type": "string",
          "description": "Order id (UUID) returned by check_coverage or create_order."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • check_coverage unknown never probed

    Free. Searches the official company register of the given country for the company name and returns the matching entities (idx, registry reference, name, address), an order id, and what a report covers. Nothing is charged. Supported country codes: GB, FR, NO, FI, CZ, EE, SK, LV, IL, CA, CY, US (CA: federal corporations only; US: SEC reporting companies only).

    mcp-tool

    {
      "type": "object",
      "required": [
        "company",
        "country"
      ],
      "properties": {
        "company": {
          "type": "string",
          "maxLength": 200,
          "minLength": 2,
          "description": "Company name to look up."
        },
        "country": {
          "type": "string",
          "description": "Two-letter country code: GB, FR, NO, FI, CZ, EE, SK, LV, IL, CA, CY, US."
        }
      },
      "additionalProperties": false
    }
    arguments 20 lines
  • create_order unknown never probed

    Selects one entity from the check_coverage results (idx, starting at 0) and returns the x402 payment requirements for a report (USDC on Base, exact amount in the requirements). This tool does not pay. To pay, send the signed payment in a PAYMENT-SIGNATURE header to the returned pay_url, then read the report with get_report.

    mcp-tool

    {
      "type": "object",
      "required": [
        "company",
        "country",
        "idx"
      ],
      "properties": {
        "idx": {
          "type": "integer",
          "minimum": 0,
          "description": "Index of the chosen entity in the check_coverage candidates."
        },
        "company": {
          "type": "string",
          "maxLength": 200,
          "minLength": 2,
          "description": "Same company name used in check_coverage."
        },
        "country": {
          "type": "string",
          "description": "Same country code used in check_coverage."
        }
      },
      "additionalProperties": false
    }
    arguments 26 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 7bad0d1ab9719dda.

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