A
licenseNot graded
qualityC
maintenanceMCP server that provides AI agents with pay-per-call access to a suite of tools (honeypot check, token market, DeFi yields, etc.) via USDC on Base using the x402 protocol.
4
MIT
sovereign-engine
Server Details
15 paid AI agent primitives via x402 (USDC on Base). Pay-per-call MCP server.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- Changed
exec_page_extract4 fields changed- added
Input schema / properties / css_selectorAdded value: +{ + "description": "Optional CSS selector for static HTML conversion", + "type": "string" +} - changed
Input schema / properties / extract_mode / descriptionPrevious value: -"preview=3K chars, full=20K chars"New value: +"preview=5K characters, full=100K characters" - added
Input schema / properties / render_modeAdded value: +{ + "description": "auto uses Browser Run only when static Markdown is insufficient", + "enum": [ + "auto", + "never", + "always" + ], + "type": "string" +} - changed
Input schema / properties / url / descriptionPrevious value: -"URL to extract content from"New value: +"Public http:// or https:// URL to convert"
6 tool updates
- Added
exec_eth_balance - Added
exec_eth_block_number - Added
exec_eth_erc20_balance - Added
exec_eth_gas_price - Added
exec_eth_nonce - Added
exec_eth_tx
2 tool updates
- Removed
cf_browser - Removed
exec_r2_store
6 tool updates
- Changed
cf_llm1 field changed- changed
Input schema / properties / model / descriptionPrevious value: -"Model name (default: openai/gpt-4o-mini)"New value: +"Model name (default: llama-3.2-11b-vision)"
- Removed
cf_llm_cached - Removed
exec_agent_passport - Removed
exec_cross_chain_route - Removed
exec_revenue_dashboard - Removed
exec_trust_bundle
4 tool updates
- Added
exec_ipfs_verify - Added
exec_trust_bundle - Added
exec_tx_preflight - Added
exec_tx_verify
1 tool update
- Removed
exec_compliance_audit
3 tool updates
- Added
exec_agent_passport - Added
exec_revenue_dashboard - Added
exec_spend_cap
15 tool updates
- First observed
cf_browser - First observed
cf_code - First observed
cf_embed - First observed
cf_image - First observed
cf_llm - First observed
cf_llm_cached - First observed
cf_stt - First observed
exec_browser_workflow - First observed
exec_compliance_audit - First observed
exec_cross_chain_route - First observed
exec_dns_audit - First observed
exec_kv_store - First observed
exec_page_extract - First observed
exec_r2_store - First observed
exec_web_search
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
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!
Related MCP Connectors
63 pay-per-call tools for agents: vision, text, data, web, blockchain. USDC on Base via x402.
Pay-per-call tools for autonomous agents, settled in USDC on Base via x402.
16130 pay-per-call APIs for AI agents: compliance, trade, safety, web, data. USDC on Base via x402.
Pay-per-call NLP & embeddings APIs on Base via x402. No keys/signup; agents pay per call in USDC.
Related MCP Servers
- FlicenseNot gradedqualityBmaintenanceA small, autonomous, pay-per-call MCP server that AI agents discover and pay for per call, with revenue landing directly in a USDC wallet on Base via the x402 payment protocol.-
- AlicenseCqualityCmaintenancex402 Micropaid MCP Server — 120+ paid API endpoints for AI Agents. Pay per call with USDC on Base network. No signup, no API key needed.551MIT
- FlicenseAqualityBmaintenanceMCP server for a live x402 payment gateway on Base (USDC). Lets AI agents discover, preview for free, then pay per call — with prepaid gasless payments, signed receipts, and delta delivery.7-
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.6/5.0
Disambiguation5/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.
Naming Consistency5/5
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.
Tool Count4/5
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.
Completeness4/5
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.