aegis
Server Details
Trust layer for the x402 economy - check any service before you pay. Scores, discovery, routing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
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.
Tool Definition Quality
Average 3.2/5 across 7 of 7 tools scored. Lowest: 2.6/5.
Each tool has a distinct purpose: discover and smart_discover both find services but one is search and the other is LLM-based; erc8004_reputation and trust_check both check reputation but one is on-chain with divergence flag and the other is verification score; procure, route, and route_batch are all distinct in their execution models (single task, single relay, batch relay). Overlaps are minimal and clearly differentiated by descriptions.
All tool names use lowercase with underscores (snake_case), which is consistent. The pattern varies: some are single verbs (discover, procure, route), some are compound (erc8004_reputation, smart_discover, route_batch, trust_check). While no mixed casing, the naming is not strictly verb_noun but maintains a predictable style.
7 tools is well-suited for a server that provides a payment/verification layer for AI services. Each tool covers a core function (discovery, reputation, procurement, routing) without excess or deficiency.
The tool set covers the main lifecycle: discovering services (discover, smart_discover), checking trust (erc8004_reputation, trust_check), procuring (procure), and routing (route, route_batch). Missing features like managing past procurenents or cancelations are minor gaps that don't hinder core functionality.
Available Tools
7 toolsdiscoverInspect
Search the Aegis registry of agent-payable services, ranked by verification-backed trust. Free.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | ||
| category | No | ||
| min_trust | No |
erc8004_reputationInspect
On-chain ERC-8004 reputation for any registered agent (Base IdentityRegistry) + Aegis probe cross-check + divergence flag. Paid $0.005 via x402 (_meta['x402/payment']).
| Name | Required | Description | Default |
|---|---|---|---|
| domain | No | ||
| agent_id | No |
procureInspect
TASK+BUDGET procurement: describe what you need in plain language + max spend; Aegis picks the best verified service, executes with failover, captures only on delivery, returns data + Ed25519-signed receipt. Never over budget. Dynamic x402 via _meta.
| Name | Required | Description | Default |
|---|---|---|---|
| need | Yes | ||
| budget | Yes |
routeInspect
Pay THROUGH Aegis: we buy the best verified service for you (by url or capability) and relay the data, failing over if one is down. One integration reaches the whole registry; not charged if nothing delivers. Dynamic x402 price via _meta.
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | ||
| capability | No |
route_batchInspect
Pay ONCE, Aegis fulfills MANY verified services with per-item failover. items=[{url|capability, params?}]. Charged only if all deliver. Dynamic x402 via _meta.
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes |
smart_discoverInspect
Describe what you need in plain language; Aegis maps it to the best verified services (LLM intent matching). Paid $0.01 via x402.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes |
trust_checkInspect
Verification-backed trust score + signals for a service before you pay it. Paid $0.01 via x402 (_meta['x402/payment']).
| Name | Required | Description | Default |
|---|---|---|---|
| url | 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.
Discussions
No comments yet. Be the first to start the discussion!