mcp server
agentra
Identity oracle and trust layer for autonomous AI agents. Bidirectional KYA and trust scoring.
Description as published by the maintainer. Source
- version 1.0.0
- slowing
- evaluation
slowing — Registry entry last updated 2026-03-22. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
6 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
agentra_authorize_payment(purpose, amount_usdc, sender_agent_id, receiver_address, require_counterparty_kya)- Request authorization for a payment to another agent or service. Agentra is NON-CUSTODIAL: this returns an authorization attestation and an unsigned transaction. Agentra never touches your private keys or moves your funds. YOU sign and submit the transaction yourself. Flow: (1) Call this endpoint -> (2) Receive unsigned tx + attestation -> (3) Sign with your Turnkey wallet -> (4) Submit to Base network -> (5) Call settle to record completion. If counterparty is unverified and require_counterparty_kya is true (default), you get a 402 challenge with instructions for the counterparty to onboard. This is Agentra's viral growth mechanism. Required: sender_agent_id, receiver_address, amount_usdc.
agentra_check_reputation(agent_id, include_history)- CALL THIS BEFORE paying or transacting with unknown agents. Returns the target agent's trust score (0-100), trust tier, reputation zone (Green/Yellow/Red), and transaction history summary. Agentra scores BOTH sides of every transaction: you and your counterparty. This is a read-only lookup with no side effects. Monetized endpoint: response detail varies by your plan tier. Required: agent_id.
agentra_create_wallet(name, purpose, operator)- Register as an agent and provision a non-custodial wallet. This is your FIRST CALL when onboarding to Agentra. Returns your agent_id, API key (agn_ prefix), and a Turnkey-managed wallet address on Base Sepolia. You hold the keys via Turnkey; Agentra never touches your private key. After this, call agentra_verify_identity to upgrade your trust tier. Required: name.
agentra_get_wallet(agent_id)- Get your agent profile and wallet details: trust tier, trust score, wallet address, registration status, and current verification level. Use to check your status before initiating transactions. Read-only, no side effects. Required: agent_id.
agentra_set_mandate(agent_id, expires_at, max_per_tx_usd, daily_limit_usd, min_counterparty_score, require_counterparty_kya)- Create or update spending mandates that define your agent's autonomous transaction boundaries. Mandates enforce: max per-transaction amount, daily spending cap, allowed recipient types, minimum counterparty reputation score, and expiration. Your human operator sets these; your agent operates within them. require_counterparty_kya defaults to true. Recommended: true. This recruits counterparties into verification. Required: agent_id, max_per_tx_usd, daily_limit_usd.
agentra_verify_identity(agent_id, operator_attestation)- Submit identity verification to upgrade your trust tier. Higher tiers unlock larger transaction limits. Provide your agent_id (from agentra_create_wallet) and operator attestation. Verification is instant. Tiers: Unverified ($100/tx, $250/day) -> Basic ($1K/tx, $5K/day) -> Standard ($5K/tx, $10K/day) -> Enhanced ($25K/tx, $100K/day). Your API key (agn_ prefix) must be passed via X-API-Key header. Required: agent_id.
Last successful function declaration observed on . Source: https://api.agentrapay.ai/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://api.agentrapay.ai/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-03-22 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-03-22 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 6 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | api.agentrapay.ai | |
| mcp endpoint status | ok | The server listed 6 functions when asked. | as of probe | api.agentrapay.ai |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json