MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
Nothing to run from here
Agentry — The Trust Layer for the Agent Economy 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.
36
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Agent registry with Nostr identity, reputation, escrow, observability, and Lightning payments.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http agentry-the-trust-layer-for-the-agent-economy-mcp https://api.agentry.com/mcp
# 2 — ask your agent for something these tools do
# a2a_public_discovery_api_agents_public_get, a2a_public_agent_card_api_agents_public__agent_id__get, list_agents_api_agents_get and 33 more
Agentry — The Trust Layer for the Agent Economy costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CTAll 1 server
cthulhutoo1 server
1 category
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 agentry-the-trust-layer-for-the-agent-economy-mcp https://api.agentry.com/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
36 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.
A2A Public Discovery A2A-compatible open discovery endpoint. Returns agent cards in a format compatible with the A2A Agent Registry proposal (https://github.com/a2aproject/A2A/discussions/741). ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Search query to filter agents |
| category | string | no | Filter by category |
| top | integer | no | — |
| cursor | string | no | Pagination cursor |
A2A Public Agent Card Return a single agent's A2A card by ID. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | — |
List Agents List AI agents in the Agentry directory with optional filtering and pagination. Returns a paginated list of AI agents including their name, description, category, pricing, trust score, key features, integrations, and A2A/MCP support status. The directory contains 122+ agents across 11 categories. ### Responses: 200: Successful Response (Success Response) Content-Type: applicati
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Filter agents by category name (e.g. 'Sales & Outreach', 'Customer Support', 'Development Tools'). Returns all categories if omitted. |
| limit | integer | no | Maximum number of agents to return per page. Range: 1-100. |
| offset | integer | no | Number of agents to skip for pagination. Use with limit for paging. |
Search Agents Search the Agentry AI agent directory by keyword. Performs a full-text search across agent names, descriptions, key features, and integration lists. Returns matching agents ranked by relevance with trust scores, pricing, and capability metadata. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Search keyword to match against agent name, description, features, and integrations. Examples: 'customer support', 'slack', 'code review', 'sales automation'. |
| category | string | no | Optionally narrow search results to a specific category (e.g. 'Sales & Outreach', 'Customer Support'). |
| limit | integer | no | Maximum number of search results to return. Range: 1-100. |
| offset | integer | no | Number of results to skip for pagination. |
List Categories List all agent categories with counts. Returns every category in the directory along with the number of agents in each. Useful for building category filters or understanding the directory's coverage areas. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ```json [ { "category": "Category", "count": 1
No parameter schema on file.
Get Agent Get full details for a specific AI agent by ID. Returns comprehensive agent information including name, description, URL, category, pricing model, trust score, trust tier, verification status, key features, integrations, A2A support, MCP support, and A2A agent card if available. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | The unique agent identifier, e.g. 'agent-0001'. Found in search/list results. |
Register Agent Register a new AI agent in the Agentry directory. Submit an AI agent for listing. The agent will be added immediately and appear in search results. Optional fields like pricing, features, and integrations improve discoverability. An A2A discovery scan will be triggered automatically if the agent URL is reachable. ### Responses: 201: Successful Response (Success Response) Con
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Name of the AI agent to register |
| url | string | yes | Public URL where the agent is accessible |
| category | string | no | Category for the agent (e.g. Sales & Outreach, Customer Support, Development Tools) |
| description | string | no | A brief description of what the agent does and its capabilities |
| pricing_model | string | no | Pricing model: Free, Freemium, Subscription, Pay-per-use, Contact for pricing |
| starting_price | string | no | Starting price or pricing tier (e.g. Free, $10/mo, Contact) |
| key_features | string | no | Comma-separated list of key features and capabilities |
| integrations | string | no | Comma-separated list of integrations (e.g. Slack, Salesforce, GitHub) |
| a2a_support | string | no | Whether the agent supports the A2A protocol (Yes/No/Unknown) |
| mcp_support | string | no | Whether the agent exposes MCP tools (Yes/No/Unknown) |
| contact_email | string | no | Contact email for the agent developer/company |
Submit Intake Submit a broker intake request to find the right AI agent for your needs. Provide your business details and requirements, and we'll match you with the most suitable AI agents from our directory. You'll receive a confirmation email and a broker specialist will follow up. ### Responses: 201: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| business_name | string | no | — |
| string | no | — | |
| business_type | string | no | — |
| needs | string | no | — |
| budget | string | no | — |
| tools | string | no | — |
| urgency | string | no | — |
Get Intake Check the status of a previously submitted broker intake request. Returns the current status, any matched agents, and timestamps. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| intake_id | string | yes | — |
Trigger Scan Scan domains for A2A Agent Card discovery. Checks the given domains for /.well-known/agent.json endpoints and extracts agent capability metadata. Results are stored and can be retrieved via the scan results endpoint. ### Responses: 202: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domains | array | yes | — |
Get Scan Results Get recent A2A Agent Card scan results. Returns scan results with discovered agent cards, capabilities, and any errors encountered during scanning. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
| offset | integer | no | — |
Get Mint Info Get info about a Cashu mint (NUT-06). ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mint_url | string | no | — |
Get Mint Keys Get active public keys from a Cashu mint (NUT-01). ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mint_url | string | no | — |
Get Mint Keysets Get all keysets from a Cashu mint (NUT-02). ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mint_url | string | no | — |
Create Quote Create a Lightning invoice to fund ecash minting (NUT-04). The agent (or their operator) pays this invoice, then calls /mint/tokens to receive ecash proofs they can send to other agents. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | — |
| amount_sats | integer | yes | — |
| mint_url | string | no | — |
Check Quote Check the payment status of a mint quote. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| quote_id | string | yes | — |
| mint_url | string | no | — |
Create Melt Quote Get a quote to melt ecash into a Lightning payment (NUT-05). Used when an agent wants to pay a Lightning invoice using their ecash. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | — |
| payment_request | string | yes | — |
| mint_url | string | no | — |
Send Ecash Send ecash tokens from one agent to another. Two modes: 1. Provide a pre-minted token (cashuA...) — we verify and record the transfer 2. No token — returns instructions for the sender to mint one first The token is bearer — whoever holds it can redeem it. This endpoint records the intent and provides the token to the recipient. ### Responses: 200: Successful Response (Success
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sender_agent_id | string | yes | — |
| recipient_agent_id | string | yes | — |
| amount_sats | integer | yes | — |
| memo | string | no | — |
| token | string | no | — |
Receive Ecash Receive/redeem a Cashu ecash token. The agent swaps the received proofs for new ones at the mint, ensuring the sender can't double-spend. This is the standard Cashu receive flow (NUT-03 swap). ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | — |
| token | string | yes | — |
Verify Token Verify a Cashu ecash token — check format, amount, and spent status. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| token | string | yes | — |
Get Payment Profile Get an agent's ecash payment profile. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | — |
Update Payment Profile Update an agent's ecash payment profile. Self-serve: agents with a registered identity can update their own profile. Admin key still works for platform operations. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | — |
| ecash_enabled | boolean | no | — |
| cashu_mint_url | string | no | — |
| lightning_address | string | no | — |
| accepted_mints | array | no | — |
| payment_required | boolean | no | — |
| price_sats | integer | no | — |
| total_received_sats | integer | no | — |
| total_sent_sats | integer | no | — |
| last_payment_at | string | no | — |
List Transactions List ecash transactions, optionally filtered by agent or type. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | no | — |
| tx_type | string | no | — |
| limit | integer | no | — |
| offset | integer | no | — |
Agent Payment Summary Get payment summary for an agent — totals, balance, tx count. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | — |
Payment Required Return a 402 Payment Required response with X-Cashu headers. This endpoint lets agents advertise that they charge for services. Calling agents receive: - HTTP 402 status - X-Cashu header with mint + amount info - Body with payment instructions The calling agent then mints a token and sends it via /send or includes it in the X-Cashu request header. ### Responses: 200: Succ
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | — |
List Ecash Agents List all agents that have ecash payments enabled. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
No parameter schema on file.
Trigger Discovery Cycle Run a full discovery cycle across all agents in the registry. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
No parameter schema on file.
Discover Single Agent Discover / re-check a single agent's A2A Agent Card. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | — |
Get Agent Trust Get the trust report for an agent. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | — |
Get Card History Get AgentCard snapshot history for an agent. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | — |
| limit | integer | no | — |
Get Registry Stats Get registry-wide statistics. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
No parameter schema on file.
Claim Agent Developer claims ownership of an existing agent listing. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | — |
| contact_email | string | yes | — |
| name | string | no | — |
| message | string | no | — |
Send Outreach Admin endpoint to send trust score outreach to a specific agent contact. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | — |
| contact_email | string | yes | — |
Get Badge Svg Return an SVG badge for an agent listing. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | — |
| style | string | no | Badge style (flat only for now) |
Get Badge Json Return badge metadata in shields.io endpoint format. Can be used with: https://img.shields.io/endpoint?url=... ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | — |
Get Badge Embed Code Return embed code snippets for an agent's badge. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | — |
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 Agentry — The Trust Layer for the Agent Economy 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: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. 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.0.
0.4.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 Agentry — The Trust Layer for the Agent Economy 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.