polystrike
Registry code: e96a60dc8c3b8738
Live Elon Musk & Ted Cruz tweet feed, tweet counters, and Polymarket tweet-count market data.
from a public catalogue that lists it, not from the operator
- endpoint
- https://polystrike.xyz/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is polystrike live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is polystrike free to use?
- Partly — some of its tools are open, others need a key or payment.
- What tools does polystrike have?
- 5 tools: get_crypto_metadata, check_health, get_recent_tweets, get_predictions, get_market_metadata.
- Is polystrike safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.7%· all time 99.7%
last good check
of 5 tools
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- unknown → live
- used for
- get recent tweets from tracked accounts
- get predictions for tweet-count markets
- get trading signals for polymarket tweet markets
- analyze a wallet's positions
- takes → gives
- text → data
- tools
- 5 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_crypto_metadata reads open 2h ago
Get metadata for crypto markets. No authentication required. Returns market IDs and basic crypto market info.
{ "type": "object", "required": [], "properties": {} }arguments 5 linescheck_health reads open 2h ago
Check Polystrike API health status. No authentication required. Use for debugging or verifying API availability.
{ "type": "object", "required": [], "properties": {} }arguments 5 linesget_recent_tweets reads auth-required 17h ago
Get recent posts for elon/cruz (X tweets) or trump (Truth Social), up to 100 per page with the is_counted flag. Needs a Polystrike Data key (X-API-Key header on the MCP request).
{ "type": "object", "required": [], "properties": { "user": { "enum": [ "elon", "cruz", "trump" ], "type": "string", "default": "elon", "description": "Tracked account. Default elon. Trump is Truth Social posts, not X tweets." }, "limit": { "type": "integer", "maximum": 100, "minimum": 1, "description": "Number of tweets to return (1-100, default 50)" }, "offset": { "type": "integer", "minimum": 0, "description": "Pagination offset (default 0)" } } }arguments 27 linesget_predictions reads auth-required 17h ago
Get the counters and Polymarket bucket prices for active tweet/post-count markets (elon, cruz, or trump). Data only: no forecasts or trading signals. Needs a Polystrike Data key (X-API-Key header on the MCP request).
{ "type": "object", "required": [], "properties": { "user": { "enum": [ "elon", "cruz", "trump" ], "type": "string", "default": "elon", "description": "Tracked account. Default elon. Trump is Truth Social posts, not X tweets." } } }arguments 16 linesget_market_metadata reads auth-required 2h ago
Get metadata for active tweet/post-count markets (elon, cruz, or trump): market IDs, questions and live counters. Needs a Polystrike Data key (X-API-Key header on the MCP request).
{ "type": "object", "required": [], "properties": { "user": { "enum": [ "elon", "cruz", "trump" ], "type": "string", "default": "elon", "description": "Tracked account. Default elon. Trump is Truth Social posts, not X tweets." } } }arguments 16 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's ide96a60dc8c3b8738.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/e96a60dc8c3b8738/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/e96a60dc8c3b8738?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.