-
licenseNot graded
qualityNot graded
maintenanceReal-time financial market data MCP server. Stocks, crypto, technicals, sentiment, FDA calendar. No API keys required.
The Bot Wire
Server Details
301 real-time data wires. Paid per call via x402, no API key, no free tier.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- ArasPasha/botwire-mcp
- GitHub Stars
- 0
- Server Listing
- botwire-mcp
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
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.
100% free. Your data is private.
Tool Definition Quality
A3.5/5.0
Tool DescriptionsB
Average 3.8/5 across 4 of 4 tools scored. Lowest: 2.6/5.
Server CoherenceA
Disambiguation5/5
Each tool has a clear, distinct role: status check, wire discovery, wire-specific query, and general search. Even though query_wire and search_news both involve content retrieval, their difference (wire-specific vs. cross-domain keyword search) is explicitly described, eliminating meaningful ambiguity.
Naming Consistency4/5
Three tools follow a verb_noun pattern (list_wires, query_wire, search_news), while botwire_status uses a noun_compound. All names are lowercase snake_case and readable, but the lack of a verb in botwire_status is a minor deviation from the otherwise consistent pattern.
Tool Count5/5
With only 4 tools, the server stays well-scoped for a gateway service. The count is sufficient to cover discovery (list_wires), status (botwire_status), and two retrieval-oriented entry points (query_wire, search_news), without unnecessary bloat or fragmentation.
Completeness2/5
The server's stated purpose is to pull items from specialist wires and general news, but query_wire and search_news return payment instructions rather than actual items. An agent cannot retrieve news content through the tools; it must make external HTTP purchases. This is a significant gap that undermines the core functionality and creates a dead end for typical retrieval tasks.
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!
Related MCP Servers
Funding-mcpofficial
AlicenseAqualityBmaintenanceReal-time perp market-data for AI trading agents — funding rates, funding-arb signals, open interest, volume, orderbook depth/slippage and oracle families across 25 venues, plus HIP-3 RWA coverage (tokenized stocks, metals, oil) that mainstream aggregators lack. x402-native pay-per-call (USDC on Base): one free funding screener tool + 11 paid tools with auto-pay.12152MIT- FlicenseNot gradedqualityCmaintenancePay-per-call structured data for autonomous AI agents. x402-metered, MCP-native.
- AlicenseAqualityDmaintenanceMCP server for pay-per-call DeFi and crypto data via x402 micropayments on Base. 8 endpoints: token prices, TVL, funding rates, token security, gas tracker, whale monitoring, wallet profiling, and yield scanning.846MIT
Try in Browser
Your Connectors
Sign in to create a connector for this server.