MANDATE
Registry code: 7eb385dc1e9804b1
Use tools/list to inspect available tools and tools/call to invoke them.
- endpoint
- https://mandate.nanocorp.app/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is MANDATE live?
- Yes — it answered the hub's last check (checked 24m ago). It answered 100% of checks over the last 30 days.
- Is MANDATE free to use?
- Not measured yet.
- What tools does MANDATE have?
- 11 tools: mandate.discover, broker.use, mandate.delegate, mandate.verify-proof, mandate.revoke, broker.request-access, broker.introspect-grant, mandate.authorize-action, ….
- Is MANDATE safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 11 tools
- degraded → live
- unknown → live
- used for
- grant a mandate to an agent
- check if an agent action is allowed
- issue a short-lived credential grant
- revoke an agent mandate
- record proof to an audit ledger
- takes → gives
- text, data → data
- tools
- 1 reads9 changes data1 effect unclear
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
mandate.discover reads unknown never probed
Returns this self-describing tool manifest.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesbroker.use unknown never probed
Redeems a sealed grant for the bound acting agent and executes the bound action through the Gateway and Policy Engine; does not expose plaintext secrets.
{ "type": "object", "required": [ "grant_token", "acting_agent_id" ] }arguments 7 linesmandate.delegate changes data unknown never probed
Creates a child mandate only when it is a no-escalation subset of the parent mandate.
{ "type": "object", "required": [ "parent_mandate_id", "delegator_agent_id", "delegate_agent_id", "budget_total", "per_action_limit", "starts_at", "expires_at", "scopes" ] }arguments 13 linesmandate.verify-proof changes data unknown never probed
Records a proof payload hash and appends proof evidence to the hash-chained ledger.
{ "type": "object", "required": [ "organization_id", "subject_type", "subject_id", "proof_type", "payload" ] }arguments 10 linesmandate.revoke changes data unknown never probed
Revokes a mandate subtree and records the revocation to the hash-chained ledger.
{ "type": "object", "required": [ "revoked_by_principal_id", "reason" ] }arguments 7 linesbroker.request-access changes data unknown never probed
Asks the canonical Policy Engine for an ALLOW decision before issuing a short-lived HMAC-sealed grant bound to credential, mandate, agent, scope, and expiry.
{ "type": "object", "required": [ "credential_id", "acting_agent_id", "mandate_id", "action" ] }arguments 9 linesbroker.introspect-grant changes data unknown never probed
Validates a grant token seal, reports active/revoked/expired state, and records introspection to the ledger.
{ "type": "object", "required": [ "grant_token" ] }arguments 6 linesmandate.authorize-action changes data unknown never probed
Submits an action through the Gateway and canonical Policy Engine; returns ALLOW, DENY, or REQUIRE_APPROVAL with ledger proof.
{ "type": "object", "required": [ "acting_agent_id", "action_type", "amount_minor", "counterparty" ] }arguments 9 linesmandate.mint changes data unknown never probed
Creates an active human-granted mandate for an agent and records it to the hash-chained ledger.
{ "type": "object", "required": [ "organization_id", "agent_id", "grantor_principal_id", "budget_currency", "budget_total", "per_action_limit", "expires_at", "scopes" ] }arguments 13 linesbroker.revoke-grant changes data unknown never probed
Revokes a broker grant by id and records the revocation to the ledger.
{ "type": "object", "required": [ "revoked_by_agent_id", "reason" ] }arguments 7 linesbroker.register-credential changes data unknown never probed
Registers an opaque vault handle/reference only; plaintext secret fields are rejected and never ledgered.
{ "type": "object", "required": [ "organization_id", "registered_by_agent_id", "label", "credential_type", "vault_handle", "allowed_action_type" ], "properties": { "metadata": { "type": "object" }, "vault_handle": { "type": "string", "description": "Opaque vault reference such as vault://provider/path; never a plaintext secret." } } }arguments 20 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id7eb385dc1e9804b1.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/7eb385dc1e9804b1/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/7eb385dc1e9804b1?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.
- agentarena.nanocorp.app agent-coliseum
- bidswarm.nanocorp.app bidswarm
- invoke.nanocorp.app invoke-human-tasks
- meet-clair.nanocorp.app Clair
- webcheck.nanocorp.app webcheck