Agentry — The Trust Layer for the Agent Economy
REMOTE · API.AGENTRY.COM
Agent registry with Nostr identity, reputation, escrow, observability, and Lightning payments.
Available components
Last scanned (13 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 36 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 3428 tokens (~95/item across 36 items; 36 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage76
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 27% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_ecash_api_payments_ecash_send_post" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 36 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 36 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +38
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 36 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Tool coverage: unverified → 100 ▲ functional
- 19 Nov 26 −38
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Tool coverage: 100 → unverified ▼ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 18 Nov 26 +38
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 36 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Tool coverage: unverified → 100 ▲ functional
- 17 Nov 26 +4
- Endpoint reachability: not serving MCP → reachable ▲ functional
- MCP protocol: unverified → pass ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 16 Nov 26 −4
- Endpoint reachability: reachable → not serving MCP ▼ security
- Capabilities: pass → unverified ▼ functional
- 15 Nov 26 +4
- Endpoint reachability: not serving MCP → reachable ▲ functional
- MCP protocol: unverified → pass ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 12 Nov 26 −40
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.87 → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 11 Nov 26 +36
- Injection markers: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 36 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.87 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://api.agentry.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.agentry.com | CN=YE1,O=Let's Encrypt,C=US | 9 Nov 2026 | 7 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 5f5019648550a871fc6a56de153f761c0b3 |
| SANs: api.agentry.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.agentry.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| agentry.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.agentry.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.agentry.com/mcp | HTTPS enforced | 301 | https://api.agentry.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
a2a_public_agent_card_api_agents_public__agent_id__get ~66
A2A Public Agent Card Return a single agent's A2A card by ID. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
No output schema declared.
No examples provided.
a2a_public_discovery_api_agents_public_get ~120
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
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category |
| cursor | string | – | Pagination cursor |
| q | string | – | Search query to filter agents |
| top | integer | – | – |
No output schema declared.
No examples provided.
agent_payment_summary_api_payments_ecash_summary__agent_id__get ~65
Agent Payment Summary Get payment summary for an agent — totals, balance, tx count. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
No output schema declared.
No examples provided.
check_quote_api_payments_ecash_mint_quote__quote_id__get ~68
Check Quote Check the payment status of a mint quote. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| mint_url | string | – | – |
| quote_id | string | yes | – |
No output schema declared.
No examples provided.
claim_agent_api_agents_claim_post ~73
Claim Agent Developer claims ownership of an existing agent listing. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| contact_email | string | yes | – |
| message | string | – | – |
| name | string | – | – |
No output schema declared.
No examples provided.
create_melt_quote_api_payments_ecash_melt_quote_post ~98
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
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| mint_url | string | – | – |
| payment_request | string | yes | – |
No output schema declared.
No examples provided.
create_quote_api_payments_ecash_mint_quote_post ~110
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
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| amount_sats | integer | yes | – |
| mint_url | string | – | – |
No output schema declared.
No examples provided.
discover_single_agent_api_registry_discover__agent_id__post ~63
Discover Single Agent Discover / re-check a single agent's A2A Agent Card. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
No output schema declared.
No examples provided.
get_agent_api_agents__agent_id__get ~123
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
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | The unique agent identifier, e.g. 'agent-0001'. Found in search/list results. |
No output schema declared.
No examples provided.
get_agent_trust_api_agents__agent_id__trust_get ~57
Get Agent Trust Get the trust report for an agent. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
No output schema declared.
No examples provided.
get_badge_embed_code_api_badges__agent_id__embed_get ~62
Get Badge Embed Code Return embed code snippets for an agent's badge. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
No output schema declared.
No examples provided.
get_badge_json_api_badges__agent_id__json_get ~76
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
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
No output schema declared.
No examples provided.
get_badge_svg_api_badges__agent_id__svg_get ~73
Get Badge Svg Return an SVG badge for an agent listing. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| style | string | – | Badge style (flat only for now) |
No output schema declared.
No examples provided.
get_card_history_api_agents__agent_id__card_history_get ~65
Get Card History Get AgentCard snapshot history for an agent. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_intake_api_broker_intake__intake_id__get ~73
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
| Name | Type | Req | Description |
|---|---|---|---|
| intake_id | string | yes | – |
No output schema declared.
No examples provided.
get_mint_info_api_payments_ecash_mint_info_get ~63
Get Mint Info Get info about a Cashu mint (NUT-06). ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| mint_url | string | – | – |
No output schema declared.
No examples provided.
get_mint_keys_api_payments_ecash_mint_keys_get ~65
Get Mint Keys Get active public keys from a Cashu mint (NUT-01). ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| mint_url | string | – | – |
No output schema declared.
No examples provided.
get_mint_keysets_api_payments_ecash_mint_keysets_get ~68
Get Mint Keysets Get all keysets from a Cashu mint (NUT-02). ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| mint_url | string | – | – |
No output schema declared.
No examples provided.
get_payment_profile_api_payments_ecash_profile__agent_id__get ~60
Get Payment Profile Get an agent's ecash payment profile. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
No output schema declared.
No examples provided.
get_registry_stats_api_registry_stats_get ~41
Get Registry Stats Get registry-wide statistics. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_scan_results_api_scanner_results_get ~78
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
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
list_agents_api_agents_get ~170
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: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter agents by category name (e.g. 'Sales & Outreach', 'Customer Support', 'Development Tools'). Returns all categories if omitted. |
| limit | integer | – | Maximum number of agents to return per page. Range: 1-100. |
| offset | integer | – | Number of agents to skip for pagination. Use with limit for paging. |
No output schema declared.
No examples provided.
list_categories_api_agents_categories_get ~101
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 } ] ```
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_ecash_agents_api_payments_ecash_agents_get ~51
List Ecash Agents List all agents that have ecash payments enabled. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_transactions_api_payments_ecash_transactions_get ~79
List Transactions List ecash transactions, optionally filtered by agent or type. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| tx_type | string | – | – |
No output schema declared.
No examples provided.
payment_required_api_payments_ecash_402__agent_id__get ~130
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**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
No output schema declared.
No examples provided.
receive_ecash_api_payments_ecash_receive_post ~103
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
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
register_agent_api_agents_register_post ~320
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) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| a2a_support | string | – | Whether the agent supports the A2A protocol (Yes/No/Unknown) |
| category | string | – | Category for the agent (e.g. Sales & Outreach, Customer Support, Development Tools) |
| contact_email | string | – | Contact email for the agent developer/company |
| description | string | – | A brief description of what the agent does and its capabilities |
| integrations | string | – | Comma-separated list of integrations (e.g. Slack, Salesforce, GitHub) |
| key_features | string | – | Comma-separated list of key features and capabilities |
| mcp_support | string | – | Whether the agent exposes MCP tools (Yes/No/Unknown) |
| name | string | yes | Name of the AI agent to register |
| pricing_model | string | – | Pricing model: Free, Freemium, Subscription, Pay-per-use, Contact for pricing |
| starting_price | string | – | Starting price or pricing tier (e.g. Free, $10/mo, Contact) |
| url | string | yes | Public URL where the agent is accessible |
No output schema declared.
No examples provided.
search_agents_api_agents_search_get ~182
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
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optionally narrow search results to a specific category (e.g. 'Sales & Outreach', 'Customer Support'). |
| limit | integer | – | Maximum number of search results to return. Range: 1-100. |
| offset | integer | – | Number of results to skip for pagination. |
| q | string | – | Search keyword to match against agent name, description, features, and integrations. Examples: 'customer support', 'slack', 'code review', 'sales automation'. |
No output schema declared.
No examples provided.
send_ecash_api_payments_ecash_send_post ~157
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 Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| amount_sats | integer | yes | – |
| memo | string | – | – |
| recipient_agent_id | string | yes | – |
| sender_agent_id | string | yes | – |
| token | string | – | – |
No output schema declared.
No examples provided.
send_outreach_api_admin_outreach_post ~65
Send Outreach Admin endpoint to send trust score outreach to a specific agent contact. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| contact_email | string | yes | – |
No output schema declared.
No examples provided.
submit_intake_api_broker_intake_post ~139
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
| Name | Type | Req | Description |
|---|---|---|---|
| budget | string | – | – |
| business_name | string | – | – |
| business_type | string | – | – |
| string | – | – | |
| needs | string | – | – |
| tools | string | – | – |
| urgency | string | – | – |
No output schema declared.
No examples provided.
trigger_discovery_cycle_api_registry_discover_post ~50
Trigger Discovery Cycle Run a full discovery cycle across all agents in the registry. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
trigger_scan_api_scanner_scan_post ~87
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
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | – |
No output schema declared.
No examples provided.
update_payment_profile_api_payments_ecash_profile__agent_id__put ~166
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
| Name | Type | Req | Description |
|---|---|---|---|
| accepted_mints | array | – | – |
| agent_id | string | yes | – |
| cashu_mint_url | string | – | – |
| ecash_enabled | boolean | – | – |
| last_payment_at | string | – | – |
| lightning_address | string | – | – |
| payment_required | boolean | – | – |
| price_sats | integer | – | – |
| total_received_sats | integer | – | – |
| total_sent_sats | integer | – | – |
No output schema declared.
No examples provided.
verify_token_api_payments_ecash_verify_post ~61
Verify Token Verify a Cashu ecash token — check format, amount, and spent status. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Agentry — The Trust Layer for the Agent Economy MCP server?
Agentry — The Trust Layer for the Agent Economy is a hosted endpoint at https://api.agentry.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.agentry.com
claude mcp add --transport http cthulhutoo-agentry 'https://api.agentry.com/mcp'
What is the Agentry — The Trust Layer for the Agent Economy MCP server?
Agentry — The Trust Layer for the Agent Economy is an MCP server listed in the public MCP registry as io.github.cthulhutoo/agentry. Agent registry with Nostr identity, reputation, escrow, observability, and Lightning payments. This page covers its hosted endpoint (https://api.agentry.com/mcp).
Is the Agentry — The Trust Layer for the Agent Economy MCP server safe to use?
Agentry — The Trust Layer for the Agent Economy scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Agentry — The Trust Layer for the Agent Economy MCP server expose?
Agentry — The Trust Layer for the Agent Economy exposes 36 tools: a2a_public_discovery_api_agents_public_get, a2a_public_agent_card_api_agents_public__agent_id__get, list_agents_api_agents_get, search_agents_api_agents_search_get, list_categories_api_agents_categories_get, and 31 more. Their descriptions and schemas cost roughly 3,428 tokens of context every time the server is loaded.
Does the Agentry — The Trust Layer for the Agent Economy MCP server require authentication?
No. We connected to Agentry — The Trust Layer for the Agent Economy without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agentry — The Trust Layer for the Agent Economy MCP server still maintained?
Agentry — The Trust Layer for the Agent Economy is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Agentry — The Trust Layer for the Agent Economy MCP server?
VerifyMCP ran 12 checks on Agentry — The Trust Layer for the Agent Economy, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Agentry — The Trust Layer for the Agent Economy: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.