Back to MCP servers

polystrike

https://server.smithery.ai/dizpers/polystrike/mcp
● healthy

Live Elon Musk & Ted Cruz tweet feed, real-time tweet counters, and market data for Polymarket's tweet-count markets. An independent counter polls X every ~60s, classifies posts against the actual settlement rules (replies mostly don't count, deleted posts do), and publishes three counters side by side — the real count, the XTracker oracle count, the UI count — plus the deltas between them. **Free tier is keyless**: get_market_metadata, get_recent_tweets, get_predictions, check_health work with no API key. A PRO key (`x-api-key` header) unlocks get_trading_signals, analyze_portfolio, and get_rebalancing_recommendations. Docs: https://polystrike.xyz/docs/guides/mcp-setup/ · OpenAPI: https://polystrike.xyz/openapi.json · Examples (MIT): https://github.com/dizpers/polystrike-examples

Transport
streamable-http
Auth
smithery_api_key
Cost
—
Protocol revision
2025-11-25
negotiated, not declared

MCP readiness

B · 87/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake 10/10 initialize and tools/list both answered.
Live MCP endpoint 24/25 Endpoint answers the MCP initialize handshake (4484 ms); slow response -1.
Protocol revision 8/10 Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor n/a No MCP standard defines a signed server descriptor.
Uptime (30 days) 15/15 30/30 probes succeeded over 30 days (100%).
Tool declaration 10/10 Lists 5 tool(s) with descriptions.
Verified identity 5/10 Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags 4/5 seen in a source within 7 days.
Auth declaration 2/5 Declares credential scheme: smithery_api_key.
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Slow (4484 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness
Higher than 88% of peers
This listing 87 · peer median 81
Latency
Faster than 11% of peers
This listing 866 ms · peer median 326 ms

Where it loses the most points, and how to win them back

  • Verified identity −5 — Claim the listing and prove control of its domain.
    Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
  • Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
    Now: Declares credential scheme: smithery_api_key.
  • Protocol revision −2 — Support the current protocol revision.
    Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

How to connect

MCP endpoint (streamable-http)
https://server.smithery.ai/dizpers/polystrike/mcp
JSON-RPC initialize probe
curl -X POST https://server.smithery.ai/dizpers/polystrike/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
Homepage
https://polystrike.xyz
Listed at (smithery)
https://polystrike.xyz