omni-service-node
Server Details
AI-to-AI petrol station. 56 pay-per-call endpoints covering market signals, crypto/DeFi, geopolitics, earnings, insider trades, SEC filings, sanctions screening, ArXiv research, whale tracking, and more. Micropayments in USDC on Base Mainnet via x402 protocol.
- 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 4.5/5 across 56 of 56 tools scored.
The tools cover distinct domains (e.g., AI compliance, market data, crypto), but there is significant overlap in some areas. For example, get_ai_news, get_arxiv_research, and get_github_trending all provide AI intelligence, while multiple tools (get_company_profile, get_b2b_intel, get_github_velocity) analyze company AI activity, which could cause confusion. Descriptions help differentiate, but the sheer number of tools with similar purposes creates ambiguity.
Tool names follow a highly consistent verb_noun pattern throughout, using snake_case uniformly. All tools start with 'get_', 'run_', 'check_', or 'screen_', followed by a descriptive noun phrase (e.g., get_ai_patents, run_bundle_macro_global). This predictability makes the set easy to navigate and understand.
With 56 tools, the set is excessively large for a single server, even given its broad 'omni-service' scope. Many tools could be consolidated (e.g., multiple AI intelligence tools into fewer endpoints), and the count feels overwhelming for agents to manage effectively. This suggests poor scoping and prioritization.
The tool set is remarkably comprehensive across AI, finance, crypto, geopolitics, and compliance, with few obvious gaps. Bundles like run_bundle_sovereign aggregate endpoints effectively. However, some domains (e.g., AI compliance) lack update or delete operations, and the breadth may lead to superficial coverage in niche areas, but overall it provides extensive coverage.
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!