mcp-registry/com.movesurge/movesurge · v1.0.0
Verdict. Movesurge MCP server answered 97.95% of Glimind's liveness checks over 30 days, better than 5% of MCP servers, with 1677 ms median handshake and 45 outages in 90 days. Its agent-readiness grade is A (91/100) across 10 tools, costing an agent about 2,634 tokens to load. Checked every few minutes; no tool is ever called.
Data as of .
| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 97.95% | 5% of MCP servers |
| Median handshake latency | 1677 ms | 8% of MCP servers |
| p95 handshake latency | 3906 ms | — |
| Checks in 30 days | 3,370 | — |
| Outages, 90 days | 45 | — |
| Median recovery | 7 min | — |
| Agent-readiness score | 91/100 (A) | 71% of MCP servers |
| Tools | 10 | — |
| Tool-list size for an agent | ~2,634 tokens | 48% of MCP servers |
| Days observed | 29 | — |
As of 2026-10-26 22:38 UTC, the Movesurge MCP server is up with a Glimind reliability score of 69/100 (grade C). Over the last 30 days it answered 98% of Glimind's liveness checks. It had 45 outages in 90 days, with a median recovery of 7 minutes.
Market news with the measured price reaction attached to the event that caused it.
Claude Code
claude mcp add --transport http movesurge-mcp-server https://movesurge.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"movesurge-mcp-server": {
"type": "http",
"url": "https://movesurge.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
1 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Reachable 98.0% of the time over the last 30 days; median recovery 7 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
Handshake + tools/list takes ~1,677 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
In the last 30 days: 0 tool(s) removed and 8 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.movesurge/movesurge"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.movesurge/movesurge"}) over MCP.
event_screen ~411 tokenseconomic_data ~371 tokensearnings ~354 tokenssearch_headlines ~335 tokensexplained_moves ~272 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.movesurge%2Fmovesurge?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.movesurge%2Fmovesurge?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.movesurge%2Fmovesurge.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.movesurge%2Fmovesurge.svg :target: https://glimind.com/server/mcp-registry%2Fcom.movesurge%2Fmovesurge?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:49dcaaff8da3e92d…, first seen 2026-10-21, included at leaf 36635 of 75,868. Version history · verify what your client received.
Compare: most reliable finance servers · most reliable search servers · most reliable communication servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 22:38 UTC, the Movesurge MCP server is up with a Glimind reliability score of 69/100 (grade C). Over the last 30 days it answered 98% of Glimind's liveness checks. It had 45 outages in 90 days, with a median recovery of 7 minutes.
Movesurge MCP server advertises 10 tools, including coverage_stats, earnings, economic_data, event_screen, explained_moves.
Point your MCP client at this streamable-http endpoint: https://movesurge.com/mcp
Glimind scanned all 10 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.