71trust / 100

Kawal

by kawal-three.vercel.app in Onchain & crypto

MCP serverPassing, checked 9 h ago

Evidence about ERC-8004 agents on BNB Smart Chain, gathered by calling them. No key.

https://kawal-three.vercel.app/api/mcp
Tools
9
open to any client
Uptime
94.1%
last 30 days
Response time
906 ms
1.4 s slowest 5%
Last check
Passed
9 h ago, next any minute now

Scan it nowHow to connect

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to connect

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "kawal": {
      "type": "http",
      "url": "https://kawal-three.vercel.app/api/mcp"
    }
  }
}

9 tools

  • verify_agent

    Call an agent's declared endpoint right now and report what answered. This is a live handshake made by Kawal, not a reading of the registry: an agent whose registration declares MCP but whose endpoint is gone is reported as not answering. Returns the hireability tier and the…

  • check_payment

    Send the opening request of the x402 protocol — no payment header — and report whether the server actually demands payment. `x402_supported` on the registry is a flag a registration sets about itself; this is the answer to asking. Kawal never settles a payment, so the price is…

  • read_reputation

    Report who wrote an agent's ERC-8004 feedback, not how much of it there is. A sample of 1,200 BSC records came from 53 addresses, one of which wrote 265 of the oldest 600, so a count of records is a count of writes rather than of opinions. Returns how many carry a mark, how many…

  • find_agents

    Search the BSC roster by describing the problem rather than naming a product, and get back agents ranked with Kawal's evidence attached. Duplicate registrations are collapsed: roughly two thirds of the newest registrations are copies of a template, and returning all of them…

  • agents_by_owner

    List the agents one wallet registered on BSC and call each of their declared endpoints now. Nothing on the chain tells an owner their endpoint went dark — the registry keeps listing it — so this is the answer to "is my agent still answering?": what answered, how each failure…

  • compare_agents

    Put two or three agents side by side and answer the same questions of each — the ones a buyer weighs before handing over a spend cap: can it be hired, does it answer right now, has it kept answering, what does it offer, what does it say it costs, does its domain verify, what is…

  • uptime_history

    Read the history Kawal keeps of one agent's endpoint without dialling it: how many times it was called, how many times it answered in the protocol it declared, since when, and the median and worst latency of the answering calls. This is the record the registry does not have…

  • plan_mandate

    Turn a capital amount and a duration into the four scoped sessions Kawal would grant on Altana — one per seat, each with its own contract allowlist, spend cap and expiry — without granting anything. Pure arithmetic over the venue table: the same plan the mandate form shows, and…

  • deep_report

    Everything Kawal holds about one agent in a single answer: the live handshake, the full probe history, how the endpoint fails when it fails, whether it really charges, and who wrote its feedback. This one costs money. Kawal measured that 75 of 200 BSC registrations declare x402…

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTime
9 h agoPassed200864 ms
20 h agoPassed200909 ms
30 h agoPassed2001.0 s
40 h agoPassed200881 ms
2 days agoPassed200938 ms
Show 10 older checks
3 days agoPassed2001.4 s
3 days agoPassed200874 ms
3 days agoPassed2001.0 s
4 days agoPassed2001.1 s
4 days agoPassed2001.3 s
5 days agoPassed200986 ms
5 days agoPassed200837 ms
5 days agoPassed200886 ms
6 days agoPassed200867 ms
6 days agoPassed200893 ms