Kawal
Server Details
Evidence about ERC-8004 agents on BNB Smart Chain, gathered by calling them. No key.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 9 tools
Most tools have distinct angles—live single check, history, paid deep report, comparison, owner sweep—so misselection is unlikely in practice. However, verify_agent, uptime_history, and deep_report all probe one agent and could be confused without reading descriptions carefully.
Six of nine tools follow the verb_noun pattern (check_payment, verify_agent, find_agents), and all names are readable snake_case. The exceptions—agents_by_owner, deep_report, and uptime_history—are noticeable but not chaotic.
Nine tools is well-scoped for a monitoring and verification service. Each tool covers a distinct user need with no obvious redundancy.
The set covers search, live verification, uptime history, reputation source analysis, payment checks, comparison, owner listing, and mandate planning. Minor gaps like pagination on agents_by_owner and find_agents prevent a higher score.
Available Tools
9 toolsagents_by_ownerEvery agent an address minted, called nowARead-onlyIdempotentInspect
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 looks, and every probe Kawal kept. At most 12 agents are dialled, so a large owner sees the first page.
Inputs: owner (required), chainId.
check_paymentAsk whether an agent really chargesARead-onlyIdempotentInspect
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 quoted in the server's own words and nothing moves.
Inputs: tokenId (required), chainId.
compare_agentsThe same questions of two or three agentsARead-onlyIdempotentInspect
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 its track record, what is flagged against it, and when it was registered. Each agent is dialled for this call. No combined score: the disagreements are the point.
Inputs: agents (required).
deep_reportEverything Kawal holds about one agent (paid)AInspect
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 support and that none of the reachable ones ever asks to be paid; this is the counter-example. Calling it without payment returns the terms rather than the report. Pay the terms with a plain BNB transfer and call again with txHash; the receipt is read on-chain and spent once.
Inputs: tokenId (required), txHash, chainId.
find_agentsSearch the roster by problemARead-onlyIdempotentInspect
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 would be returning the same agent many times. With trending, the list is instead what 8004scan's visitors looked at most over that window — attention, not evidence — each entry carrying the tier Kawal's own record gives it, which is where the two disagree.
Inputs: limit, query, chainId, trending.
plan_mandatePlan four bounded seats for a capital amountARead-onlyIdempotentInspect
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 the same refusals, since a plan that would widen authority (an unproven venue, an empty allowlist, caps that overcommit) is refused rather than built.
Inputs: days (required), capitalUsdt (required), chainId.
read_reputationWho wrote an agent's feedbackARead-onlyIdempotentInspect
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 distinct addresses wrote them, and what share came from the busiest one.
Inputs: tokenId (required), chainId.
uptime_historyEvery probe Kawal has made of an agentARead-onlyIdempotentInspect
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. Null when Kawal has never called this endpoint; verify_agent makes the first call.
Inputs: tokenId (required), chainId.
verify_agentVerify an agent by calling itARead-onlyIdempotentInspect
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 evidence behind it, including how many times Kawal has reached this endpoint before.
Inputs: tokenId (required), chainId.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Find and vet AI agents on BNB Chain by on-chain evidence: ERC-8004 registry, ERC-8183 escrow, free
Credit records and scores of ERC-8004 AI agents on Robinhood Chain, from Priors. No key needed.
Find ERC-8004 agents on Ethereum and Base whose MCP or A2A endpoints actually answer.
378k+ ERC-8004 agents and their security verifications. Two tools free, the rest USDC over x402.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceLets you probe ERC-8004 agents on BNB Smart Chain by calling their declared MCP or A2A endpoints, checking payment requirements, reading on-chain reputation authorship, and finding agents by description.MIT
- FlicenseNot gradedqualityBmaintenanceLets agents discover, verify, and inspect x402/B402 payment endpoints on BNB Chain, with read-only tools to list skills, check live counter behavior, and review the settlement tape.-
- AlicenseAqualityDmaintenanceTrust scoring, scam detection, and EAS attestations for ERC-8004 + x402 agents on Base.1871 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables users to search the on-chain index of 378,000+ ERC-8004 agents and read Cybercentry verification results spanning token, code, media, web, and wallet dimensions.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.