Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
Kawal is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
9
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Evidence about ERC-8004 agents on BNB Smart Chain, gathered by calling them. No key.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http kawal-mcp https://kawal-three.vercel.app/api/mcp
# 2 — ask your agent for something these tools do
# verify_agent, check_payment, read_reputation and 6 more
Kawal costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PUAll 4 servers
PugarHuda4 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http kawal-mcp https://kawal-three.vercel.app/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chainId | number | no | Chain id. One of 56, 97. Defaults to 56. |
| tokenId | string | yes | ERC-8004 token id, decimal digits. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chainId | number | no | Chain id. One of 56, 97. Defaults to 56. |
| tokenId | string | yes | ERC-8004 token id, decimal digits. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chainId | number | no | Chain id. One of 56, 97. Defaults to 56. |
| tokenId | string | yes | ERC-8004 token id, decimal digits. |
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 ov
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | What you need done, in plain words. Optional when trending is given; then it filters the trending list by name or description. |
| trending | string | no | Return 8004scan's trending agents for this window instead of a search, in the registry's order. |
| limit | number | no | How many to return, at most 20. |
| chainId | number | no | Chain id. One of 56, 97. Defaults to 56. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| owner | string | yes | The wallet that minted the registrations: 0x followed by forty hex characters. address is accepted as an alias. |
| chainId | number | no | Chain id. One of 56, 97. Defaults to 56. |
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 combine
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agents | array | yes | One to 3 agents to compare. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chainId | number | no | Chain id. One of 56, 97. Defaults to 56. |
| tokenId | string | yes | ERC-8004 token id, decimal digits. |
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)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| capitalUsdt | number | yes | Capital to entrust, in USDT. Positive, at most 1000000000000. |
| days | integer | yes | How long the mandate runs, in whole days. 1 to 365. |
| chainId | number | no | Chain id. One of 56, 97. Defaults to 56. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chainId | number | no | Chain id. One of 56, 97. Defaults to 56. |
| tokenId | string | yes | ERC-8004 token id, decimal digits. |
| txHash | string | no | Hash of the BNB transfer that paid the terms: 0x followed by 64 hex characters. Omit to receive the terms. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Kawal or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Kawal can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.