Access control for AI agents and MCP servers: allow, hold for approval, or block each tool call
Kya Brasil 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.
What it does
KYA backed by a real company: e-CNPJ-signed agent mandates, revocation-checked, signed verdicts
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http kya-brasil-mcp https://kya-br-agents.marcelfons.workers.dev/mcp
# 2 — ask your agent for something these tools do
# kya_register, kya_verify_paid, kya_check_action and 12 more
Kya Brasil costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 kya-brasil-mcp https://kya-br-agents.marcelfons.workers.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
15 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.
Register an AI agent for a Brazilian company: agent key (EVM address or Web Bot Auth Ed25519 key), CNPJ and a mandate (JSON, validated against /.well-known/kya-mandate.schema.json). Returns a one-time challenge the agent signs with its key and the company signs with its e-CNPJ (CMS/PKCS#7). Price covers the checks at issuance.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent | object | yes | — |
| cnpj | string | no | The company's CNPJ (company agents). Leave out with principal "person". |
| principal | string | no | "person": the agent acts for a natural person who signs with an e-CPF (no CNPJ; no name or CPF is ever published). |
| mandate | object | yes | Mandate JSON validated by https://kya-br-agents.marcelfons.workers.dev/.well-known/kya-mandate.schema.json. Reserved fields: actions, max_per_operation, max_per_day, currencies, counterparties, valid_ |
Same as the free verification, without daily limit, plus a signed receipt of the verification itself (what was checked, when). Pay per call with x402.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credential_id | string | yes | credential_id returned by kya_register. |
Signed verdict: is this action (action, amount, currency, counterparty, payment instrument) inside the agent's mandate and is the credential active? Evaluates the reserved mandate fields; lists the fields it did not evaluate.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credential_id | string | yes | credential_id returned by kya_register. |
| action | string | no | Action the agent wants to perform (e.g. pay, order, sign). |
| amount | number | no | — |
| currency | string | no | BRL, USDC, ... |
| counterparty | string | no | CNPJ, domain or wallet address of the other side. |
| spent_today | number | no | What this agent already spent today, if you track it (used for max_per_day). |
| payment_network | string | no | Payment network or rail of this operation: visa, mastercard, elo, pix, ... |
| payment_ref_sha256 | string | no | SHA-256 hex of the payment token reference or PAR used (never a card number); checked against mandate.payment_instruments. |
Re-issue the credential for 90 more days. The company signs the renewal challenge with an e-CNPJ in force (not revoked); the company must still be ATIVA at the Receita.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credential_id | string | yes | credential_id returned by kya_register. |
Free. Send both signatures of the challenge. The e-CNPJ chain is validated against ICP-Brasil roots, the CNPJ must match, the certificate must not be revoked (CRL) and the company must be ATIVA; then the credential is issued (90 days, Ed25519-signed).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credential_id | string | yes | credential_id returned by kya_register. |
| challenge_id | string | yes | challenge.id from kya_register (or kya_renew). |
| agent_signature | string | yes | Signature of challenge.text by the agent key: EIP-191 personal_sign hex (evm) or raw Ed25519 base64url (web-bot-auth). |
| ecnpj_signature | string | yes | CMS/PKCS#7 SignedData (detached, base64 DER) of challenge.text, signed with the company's e-CNPJ certificate. |
Signed answer ($0.01) for a person's agent (principal.kind person): does the CPF you already have match the e-CPF holder behind it? On a match, a subject_ref of your own for that person (stable for you, different for every verifier). The CPF is never stored, published or revealed; 3 non-matching answers per credential stop your checks. The person sees every check.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credential_id | string | yes | credential_id returned by kya_register. |
| cpf | string | yes | The CPF you already have for this person; used for the comparison only, never stored. |
Free, person only: every live credential behind your e-CPF and every CPF check made against each one. Sign "KYA Brasil: my agents at: <ISO time>" with the e-CPF (valid 10 minutes).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| signed_text | string | yes | "KYA Brasil: my agents at: <ISO time>" |
| ecpf_signature | string | yes | CMS/PKCS#7 of signed_text with the person's e-CPF, base64 DER. |
Free. Link for whoever holds the company's e-CNPJ (owner, accountant): give challenge_id and the agent's signature, get the /sign URL. They see agent, company and mandate and sign in the browser (A1 .pfx) or with any ICP-Brasil signer (A3 token, cloud), or run kya-sign (npm @kya-brasil/agent-tools) with the link. The issuer never sees the certificate.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credential_id | string | yes | credential_id returned by kya_register. |
| challenge_id | string | yes | challenge.id from kya_register or kya_renew. |
| agent_signature | string | no | The agent's signature of challenge.text, so the person only signs with the e-CNPJ. |
Free (50/day per IP). The agent's current credential: principal company, mandate, status (active, suspended, revoked, expired) and signature. Also by key: /v1/agents/by-key?kind=&id=.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credential_id | string | no | credential_id returned by kya_register. |
| agent | object | no | Alternative to credential_id: look up active credentials by agent key. |
Free. Second step of kya_renew: send both signatures of the renewal challenge; the credential is re-issued for 90 days if the e-CNPJ is not revoked and the company is still ATIVA.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credential_id | string | yes | credential_id returned by kya_register. |
| challenge_id | string | yes | challenge.id from kya_register (or kya_renew). |
| agent_signature | string | yes | Signature of challenge.text by the agent key: EIP-191 personal_sign hex (evm) or raw Ed25519 base64url (web-bot-auth). |
| ecnpj_signature | string | yes | CMS/PKCS#7 SignedData (detached, base64 DER) of challenge.text, signed with the company's e-CNPJ certificate. |
Free. The company revokes the credential at once (e-CNPJ-signed request). Revocations are listed at /v1/revocations.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credential_id | string | yes | credential_id returned by kya_register. |
| signed_text | string | yes | Exactly "KYA Brasil: revoke <credential_id>" followed by a newline and a nonce of your choice. |
| ecnpj_signature | string | yes | CMS/PKCS#7 SignedData (detached, base64 DER) of signed_text with the company's e-CNPJ. |
| reason | string | no | — |
Free, company only. Every credential ever registered for your CNPJ, any status, whoever held the certificate (an accountant, another employee). Request signed with your e-CNPJ over "KYA Brasil: agents <cnpj>" + "at: <ISO time>".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cnpj | string | yes | The company's CNPJ. |
| signed_text | string | yes | "KYA Brasil: <agents|webhook> <cnpj>", for the webhook a "url: <https url or ->" line, then "at: <ISO time>" (within 10 minutes). |
| ecnpj_signature | string | yes | CMS/PKCS#7 SignedData of signed_text with the company's e-CNPJ, detached, base64 DER. |
Free, company only. Sets the https URL that receives signed events about your agents: credential issued, renewed, suspended, reinstated, revoked. Request signed with your e-CNPJ; url "-" removes it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cnpj | string | yes | The company's CNPJ. |
| signed_text | string | yes | "KYA Brasil: <agents|webhook> <cnpj>", for the webhook a "url: <https url or ->" line, then "at: <ISO time>" (within 10 minutes). |
| ecnpj_signature | string | yes | CMS/PKCS#7 SignedData of signed_text with the company's e-CNPJ, detached, base64 DER. |
Free. Credentials revoked since a date (default: last 30 days), for verifiers that cache credentials.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since | string | no | — |
Free. What KYA Brasil is, how the credential flow works, prices, and where the schemas and signing keys are.
No parameter schema on file.
- 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 Kya Brasil or to call it, at any volume.
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.4.1.
No release note was published with this version.
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.
Any signed-in account that does not publish Kya Brasil can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.