xactions
Registry code: d697dddd5fbd96ed
XActions reads public X/Twitter data with no API key and no login. Use x_profile and x_posts to research an account, x_post and x_thread to read a specific conversation, x_video to pull a downloadable MP4, and xactions_docs before writing any XActions automation. Everything is read-only: nothing here posts, follows, or changes an account.
- endpoint
- https://xactions.app/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 xactions live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is xactions free to use?
- No — it charges per call, from 0.001 USDC, quoted in its own 402 answers.
- What tools does xactions have?
- 6 tools: x_post, x_posts, x_video, x_thread, xactions_docs, x_profile.
- Is xactions 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.3%· all time 99.3%
last good check
of 6 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- topic
- communication social media
- used for
- read an x profile
- read recent x posts
- read an x thread
- download an x video
- takes → gives
- text → data, video
- tools
- 6 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.
x_profile reads 0.001 USDC paid 5h ago
Public profile for one X/Twitter account: display name, bio, location, website, join date, follower and following counts, post count, avatar and banner, verification, and pinned post. Accepts a handle, @handle, or profile URL. No API key, no login. (costs $0.001000 in USDC via x402)
{ "type": "object", "required": [ "handle" ], "properties": { "handle": { "type": "string", "description": "Handle, @handle, or profile URL. Example: \"nasa\", \"@nasa\", \"https://x.com/nasa\"." } }, "additionalProperties": false }arguments 13 linesx_post reads unknown never probed
One public X/Twitter post in full: text (including long-form posts past 280 characters), author, timestamp, every public metric (likes, reposts, replies, quotes, bookmarks, views), attached media with direct URLs, hashtags, mentions, expanded links, and the quoted post if there is one.
{ "type": "object", "required": [ "post" ], "properties": { "post": { "type": "string", "description": "Post ID or x.com status URL." } }, "additionalProperties": false }arguments 13 linesx_posts reads unknown never probed
The most recent posts from one X/Twitter account, newest first, with text, timestamps, engagement metrics, and media. Use this to see what someone has been posting about before writing about them or replying to them. (costs $0.005000 in USDC via x402)
{ "type": "object", "required": [ "handle" ], "properties": { "limit": { "type": "integer", "maximum": 100, "minimum": 1, "description": "How many posts to return, 1 to 100. Default 20." }, "handle": { "type": "string", "description": "Handle, @handle, or profile URL." } }, "additionalProperties": false }arguments 19 linesx_video reads unknown 5h ago
Every downloadable MP4 for a post that contains a video or GIF, best quality first, with width, height and bitrate, plus a ready-to-use download link that streams the file with a proper filename. Returns a clear error when the post holds no video.
{ "type": "object", "required": [ "post" ], "properties": { "post": { "type": "string", "description": "Post ID or x.com status URL." } }, "additionalProperties": false }arguments 13 linesx_thread reads unknown 1h ago
The conversation around a post, in order: every post above it up to the root, and the author's own continuation below it. Give it any post in a thread and it returns the thread. Use this instead of x_post when the post you have is part of a longer argument.
{ "type": "object", "required": [ "post" ], "properties": { "post": { "type": "string", "description": "Any post ID or x.com status URL in the thread." }, "limit": { "type": "integer", "maximum": 50, "minimum": 1, "description": "Maximum posts to return, 1 to 50. Default 25." } }, "additionalProperties": false }arguments 19 linesxactions_docs reads unknown 5h ago
Search everything XActions ships: guides, tutorials, the CLI and API reference, all 49 agent skills, and every browser script, returning the matching passages with their source URLs. Use this before writing XActions code, or when the user asks how to automate something on X.
{ "type": "object", "required": [ "query" ], "properties": { "limit": { "type": "integer", "maximum": 20, "minimum": 1, "description": "How many passages to return, 1 to 20. Default 6." }, "query": { "type": "string", "description": "What you want to know. A natural question works better than keywords." } }, "additionalProperties": false }arguments 19 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 idd697dddd5fbd96ed.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/d697dddd5fbd96ed/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/d697dddd5fbd96ed?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.