_ registry / mcp streamable-http · checked 4m ago

ktozvonil-mcp

https://ktozvonil.net

Registry code: aaf13d88158dc4cb

api record

Who-called phone lookups: community verdict, spam rating, operator and reviews (ktozvonil.net).

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

endpoint
https://ktozvonil.net/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 ktozvonil-mcp live?
Yes — it answered the hub's last check (checked 4m ago). It answered 98% of checks over the last 30 days.
Is ktozvonil-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does ktozvonil-mcp have?
2 tools: post_comment, lookup_phone.
Is ktozvonil-mcp 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.3%

90 days 97.9%· all time 97.9%

latency
291ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 331 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
  • look up who called from a phone number
  • check spam rating of a number
  • post a review of a phone number
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
1 open 1 never probed 1 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.

  • lookup_phone reads open 13h ago

    Look up a phone number on ktozvonil.net: community verdict, rating, spam level, operator, region, tags and recent reviews.

    mcp-tool

    {
      "type": "object",
      "required": [
        "number"
      ],
      "properties": {
        "number": {
          "type": "string",
          "description": "Phone number (digits, international or local format)"
        }
      }
    }
    arguments 12 lines
  • post_comment changes data unknown never probed

    Post a phone-number review on behalf of the authenticated user. Requires an OAuth access token with the "write" scope (discover via /.well-known/oauth-protected-resource). The review is labelled AI-agent-generated, shown in a separate section, and does NOT affect the community rating or verdict.

    mcp-tool

    {
      "type": "object",
      "required": [
        "number",
        "rating",
        "text"
      ],
      "properties": {
        "text": {
          "type": "string",
          "description": "Review text (min 3 chars)"
        },
        "number": {
          "type": "string",
          "description": "Phone number (digits, international or local format)"
        },
        "rating": {
          "type": "integer",
          "description": "Star rating 1-5 (1 = dangerous/spam, 5 = safe/trusted)"
        }
      }
    }
    arguments 22 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 aaf13d88158dc4cb.

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