_ registry / mcp + a2a http-sse · checked 19h ago

inbox-check-guest

https://check.live-direct-marketing.online

Registry code: fe0b3770de0f4166

api record

No Inbox Check registration, API key, email-login or Telegram is required for these guest tools. Start with guest_providers_list, then guest_tests_create with the sender email and optional providers. Save the returned token and send_to addresses. Creation is not a delivery result: the user must send their actual message to these addresses, or explicitly authorize their own sender integration. Poll guest_tests_get with the saved token; stop at done/expired, honour 429 and Retry-After, and do not recreate tests on timeout. Report measured evidence only; pending is not delivered. Interpret…

endpoint
https://check.live-direct-marketing.online/mcp
door code
0e4e4e1b02e045ad
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 inbox-check-guest live?
Yes — it answered the hub's last check (checked 19h ago). It answered 100% of checks over the last 30 days.
Is inbox-check-guest free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does inbox-check-guest have?
3 tools: guest_tests_create, guest_providers_list, guest_tests_get.
Is inbox-check-guest 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 99.1%· all time 100%

latency
103ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 110 checks · signed record
  • unknown → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • 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 3 tools
1 open1 auth-required 1 never probed 2 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.

  • guest_providers_list open 19h ago

    List currently available free test providers; no account or API key.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • guest_tests_get auth-required 19h ago

    Read a guest test by its saved private report token, including measured results and ai_context. Pending is not delivery. No test listing, deletion or managed-key reports.

    mcp-tool

    {
  "type": "object",
  "required": [
    "token"
  ],
  "properties": {
    "token": {
      "type": "string",
      "pattern": "^[A-Za-z0-9_-]+$",
      "maxLength": 256,
      "minLength": 1
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • guest_tests_create unknown never probed

    Create one free inbox-placement test. Requires sender email, not email-login. Returns token and seed addresses; send the real message before polling for measured results. Notification emails default off. Never automatically replay this POST.

    mcp-tool

    {
  "type": "object",
  "required": [
    "email"
  ],
  "properties": {
    "email": {
      "type": "string",
      "format": "email",
      "maxLength": 200
    },
    "providers": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 20
    },
    "emailLocale": {
      "enum": [
        "en",
        "ru"
      ],
      "type": "string"
    },
    "senderLinkReports": {
      "type": "boolean",
      "default": false
    },
    "finalReportEnabled": {
      "type": "boolean",
      "default": false
    },
    "placementChangeAlertsEnabled": {
      "type": "boolean",
      "default": false
    }
  },
  "additionalProperties": false
}
    arguments 40 lines
_ try it over mcp 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 fe0b3770de0f4166.

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

_ also on live-direct-marketing.online 3 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.