Agent registry with Nostr identity, reputation, escrow, observability, and Lightning payments.
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Average 3/5 across 36 of 36 tools scored. Lowest: 2.3/5.
Most tools have distinct purposes, but some overlap exists. For example, 'a2a_public_agent_card_api_agents_public__agent_id__get' and 'get_agent_api_agents__agent_id__get' both retrieve agent information, though one focuses on A2A cards and the other on comprehensive details. Similarly, 'discover_single_agent_api_registry_discover__agent_id__post' and 'trigger_discovery_cycle_api_registry_discover_post' relate to discovery but serve different scopes. Descriptions help clarify, but an agent might occasionally misselect between these closely related tools.
Naming is mixed, with a general pattern of snake_case but inconsistent verb usage. Tools like 'list_agents_api_agents_get' and 'search_agents_api_agents_search_get' follow a verb_noun_api_path pattern, but others like 'a2a_public_agent_card_api_agents_public__agent_id__get' are overly verbose and include API path details, making them less readable. There's no uniform convention across all tools, though they remain decipherable with effort.
With 36 tools, the count is excessive for the server's purpose as a trust layer for the agent economy. Many tools, such as multiple badge-related endpoints (e.g., 'get_badge_embed_code_api_badges__agent_id__embed_get', 'get_badge_json_api_badges__agent_id__json_get', 'get_badge_svg_api_badges__agent_id__svg_get') and various payment operations, could be consolidated or streamlined. This bloated set may overwhelm agents and reduce usability.
The tool set provides comprehensive coverage for the domain, including agent registration, discovery, trust scoring, payment handling (ecash minting, melting, sending, receiving), and administrative functions. There are no obvious gaps; agents can perform full CRUD-like operations on agents, manage payments, and access registry statistics, ensuring a complete workflow for the agent economy.
a2a_public_agent_card_api_agents_public__agent_id__getInspectA2A Public Agent Card
Return a single agent's A2A card by ID.
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes |
a2a_public_discovery_api_agents_public_getInspectA2A 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).
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Search query to filter agents | |
| top | No | ||
| cursor | No | Pagination cursor | |
| category | No | Filter by category |
agent_payment_summary_api_payments_ecash_summary__agent_id__getInspectAgent Payment Summary
Get payment summary for an agent — totals, balance, tx count.
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes |
check_quote_api_payments_ecash_mint_quote__quote_id__getInspectCheck Quote
Check the payment status of a mint quote.
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| mint_url | No | https://mint.minibits.cash/Bitcoin | |
| quote_id | Yes |
claim_agent_api_agents_claim_postInspectClaim Agent
Developer claims ownership of an existing agent listing.
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | ||
| message | No | ||
| agent_id | Yes | ||
| contact_email | Yes |
create_melt_quote_api_payments_ecash_melt_quote_postInspectCreate 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.
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes | ||
| mint_url | No | ||
| payment_request | Yes |
create_quote_api_payments_ecash_mint_quote_postInspectCreate 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.
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes | ||
| mint_url | No | ||
| amount_sats | Yes |
discover_single_agent_api_registry_discover__agent_id__postInspectDiscover Single Agent
Discover / re-check a single agent's A2A Agent Card.
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes |
get_agent_api_agents__agent_id__getInspectGet 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.
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes | The unique agent identifier, e.g. 'agent-0001'. Found in search/list results. |
get_agent_trust_api_agents__agent_id__trust_getInspectGet Agent Trust
Get the trust report for an agent.
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes |
get_badge_embed_code_api_badges__agent_id__embed_getInspectGet Badge Embed Code
Return embed code snippets for an agent's badge.
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes |
get_badge_json_api_badges__agent_id__json_getInspectGet Badge Json
Return badge metadata in shields.io endpoint format.
Can be used with: https://img.shields.io/endpoint?url=...
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes |
get_badge_svg_api_badges__agent_id__svg_getInspectGet Badge Svg
Return an SVG badge for an agent listing.
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| style | No | Badge style (flat only for now) | flat |
| agent_id | Yes |
get_card_history_api_agents__agent_id__card_history_getInspectGet Card History
Get AgentCard snapshot history for an agent.
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| agent_id | Yes |
get_intake_api_broker_intake__intake_id__getInspectGet Intake
Check the status of a previously submitted broker intake request.
Returns the current status, any matched agents, and timestamps.
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| intake_id | Yes |
get_mint_info_api_payments_ecash_mint_info_getInspectGet Mint Info
Get info about a Cashu mint (NUT-06).
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| mint_url | No | https://mint.minibits.cash/Bitcoin |
get_mint_keys_api_payments_ecash_mint_keys_getInspectGet Mint Keys
Get active public keys from a Cashu mint (NUT-01).
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| mint_url | No | https://mint.minibits.cash/Bitcoin |
get_mint_keysets_api_payments_ecash_mint_keysets_getInspectGet Mint Keysets
Get all keysets from a Cashu mint (NUT-02).
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| mint_url | No | https://mint.minibits.cash/Bitcoin |
get_payment_profile_api_payments_ecash_profile__agent_id__getInspectGet Payment Profile
Get an agent's ecash payment profile.
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes |
get_registry_stats_api_registry_stats_getInspectGet Registry Stats
Get registry-wide statistics.
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_scan_results_api_scanner_results_getInspectGet Scan Results
Get recent A2A Agent Card scan results.
Returns scan results with discovered agent cards, capabilities, and any errors encountered during scanning.
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| offset | No |
list_agents_api_agents_getInspectList 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.
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of agents to return per page. Range: 1-100. | |
| offset | No | Number of agents to skip for pagination. Use with limit for paging. | |
| category | No | Filter agents by category name (e.g. 'Sales & Outreach', 'Customer Support', 'Development Tools'). Returns all categories if omitted. |
list_categories_api_agents_categories_getInspectList 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.
200: Successful Response (Success Response) Content-Type: application/json
Example Response:
[
{
"category": "Category",
"count": 1
}
]| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_ecash_agents_api_payments_ecash_agents_getInspectList Ecash Agents
List all agents that have ecash payments enabled.
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_transactions_api_payments_ecash_transactions_getInspectList Transactions
List ecash transactions, optionally filtered by agent or type.
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| offset | No | ||
| tx_type | No | ||
| agent_id | No |
payment_required_api_payments_ecash_402__agent_id__getInspectPayment 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.
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes |
receive_ecash_api_payments_ecash_receive_postInspectReceive 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).
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| token | Yes | ||
| agent_id | Yes |
register_agent_api_agents_register_postInspectRegister 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.
201: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Public URL where the agent is accessible | |
| name | Yes | Name of the AI agent to register | |
| category | No | Category for the agent (e.g. Sales & Outreach, Customer Support, Development Tools) | Uncategorized |
| a2a_support | No | Whether the agent supports the A2A protocol (Yes/No/Unknown) | Unknown |
| description | No | A brief description of what the agent does and its capabilities | |
| mcp_support | No | Whether the agent exposes MCP tools (Yes/No/Unknown) | Unknown |
| integrations | No | Comma-separated list of integrations (e.g. Slack, Salesforce, GitHub) | |
| key_features | No | Comma-separated list of key features and capabilities | |
| contact_email | No | Contact email for the agent developer/company | |
| pricing_model | No | Pricing model: Free, Freemium, Subscription, Pay-per-use, Contact for pricing | Unknown |
| starting_price | No | Starting price or pricing tier (e.g. Free, $10/mo, Contact) | Unknown |
search_agents_api_agents_search_getInspectSearch 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.
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Search keyword to match against agent name, description, features, and integrations. Examples: 'customer support', 'slack', 'code review', 'sales automation'. | |
| limit | No | Maximum number of search results to return. Range: 1-100. | |
| offset | No | Number of results to skip for pagination. | |
| category | No | Optionally narrow search results to a specific category (e.g. 'Sales & Outreach', 'Customer Support'). |
send_ecash_api_payments_ecash_send_postInspectSend Ecash
Send ecash tokens from one agent to another.
Two modes:
Provide a pre-minted token (cashuA...) — we verify and record the transfer
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.
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| memo | No | ||
| token | No | ||
| amount_sats | Yes | ||
| sender_agent_id | Yes | ||
| recipient_agent_id | Yes |
send_outreach_api_admin_outreach_postInspectSend Outreach
Admin endpoint to send trust score outreach to a specific agent contact.
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes | ||
| contact_email | Yes |
submit_intake_api_broker_intake_postInspectSubmit 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.
201: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| No | |||
| needs | No | ||
| tools | No | ||
| budget | No | ||
| urgency | No | exploring | |
| business_name | No | ||
| business_type | No |
trigger_discovery_cycle_api_registry_discover_postInspectTrigger Discovery Cycle
Run a full discovery cycle across all agents in the registry.
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
trigger_scan_api_scanner_scan_postInspectTrigger 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.
202: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| domains | Yes |
update_payment_profile_api_payments_ecash_profile__agent_id__putInspectUpdate 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.
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes | ||
| price_sats | No | ||
| ecash_enabled | No | ||
| accepted_mints | No | ||
| cashu_mint_url | No | ||
| last_payment_at | No | ||
| total_sent_sats | No | ||
| payment_required | No | ||
| lightning_address | No | ||
| total_received_sats | No |
verify_token_api_payments_ecash_verify_postInspectVerify Token
Verify a Cashu ecash token — check format, amount, and spent status.
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
| token | Yes |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Sign in to create a connector for this server.