sovereign-engine
Server Details
15 paid AI agent primitives via x402 (USDC on Base). Pay-per-call MCP server.
- Status
- Unhealthy
- 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.4/5 across 20 of 20 tools scored. Lowest: 2.8/5.
Each tool has a clearly distinct purpose. The 'cf_' tools cover different AI capabilities (code execution, embeddings, image gen, LLM, STT), while 'exec_' tools range from DNS audits to Ethereum operations to browser automation. Even similar-sounding tools like exec_eth_balance and exec_eth_erc20_balance are distinct (native vs token). No significant overlap.
The naming follows a consistent pattern across two prefixes: 'cf_' for Cloudflare tasks (verb-based) and 'exec_' for execution tasks (exec_domain_action or exec_domain_noun). All names are snake_case, descriptive, and follow the same structural conventions, making it predictable.
20 tools is on the higher end but appropriate given the server's broad scope covering multiple domains (AI, blockchain, web services, storage). Each tool serves a distinct function, and the count doesn't feel excessive for a general-purpose utility server.
Most domains are reasonably covered. Ethereum operations include balance, ERC20, gas, nonce, tx details, preflight, and verify—though a broadcast/send tool is missing. Cloudflare lacks text-to-speech or translation. However, the core workflows are present, and minor gaps don't hinder overall usability.
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!