postcopilot-mcp
Registry code: c0d87b60a25766fa
Threads tools for AI — generate viral posts, download videos, export profiles
from a public catalogue that lists it, not from the operator
- endpoint
- https://postcopilot.ai/mcp
- protocol
- http-sse ·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 postcopilot-mcp live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 97% of checks over the last 30 days.
- Is postcopilot-mcp free to use?
- Not measured yet.
- What tools does postcopilot-mcp have?
- 6 tools: postcopilot_generate_post, postcopilot_download_video, postcopilot_export_profile, postcopilot_export_followers, postcopilot_export_following, postcopilot_read_guide.
- Is postcopilot-mcp 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 97.5%· all time 97.5%
last good check
of 6 tools
- degraded → live
- live → degraded· timeout after 20000ms
- down → live
- degraded → down· timeout after 20000ms
- live → degraded· timeout after 20000ms
- topic
- communication social media
- used for
- generate a threads post
- download video from a threads post
- export followers of a threads profile
- export recent posts of a threads user
- takes → gives
- text, web pages → 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.
postcopilot_generate_post reads unknown never probed
Generate a viral Threads post using a fine-tuned AI model. Provide a topic or idea and get a ready-to-post caption. Returns the generated text.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "message" ], "properties": { "model": { "enum": [ "gpt", "llama" ], "type": "string", "default": "gpt", "description": "AI model to use: 'gpt' (fine-tuned GPT, default) or 'llama' (Together AI Llama)" }, "message": { "type": "string", "description": "The topic, idea, or prompt for the Threads post" } } }arguments 22 linespostcopilot_download_video reads unknown never probed
Download a video from a Threads post URL. Returns direct video download URLs (no watermark). The URL must be a Threads post containing a video (e.g. https://www.threads.com/@user/post/ABC123).
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "url" ], "properties": { "url": { "type": "string", "format": "uri", "description": "The Threads post URL containing the video" } } }arguments 14 linespostcopilot_export_profile reads unknown never probed
Export up to 20 recent posts from a Threads user profile. Returns structured post data including text, likes, replies, reposts, and timestamps. Provide a profile URL like https://www.threads.com/@username.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "url" ], "properties": { "url": { "type": "string", "format": "uri", "description": "The Threads profile URL (e.g. https://www.threads.com/@username)" } } }arguments 14 linespostcopilot_export_followers reads unknown never probed
Export up to 60 followers from a Threads user profile. Returns usernames, display names, follower counts, and verification status. Provide a profile URL like https://www.threads.com/@username.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "url" ], "properties": { "url": { "type": "string", "format": "uri", "description": "The Threads profile URL (e.g. https://www.threads.com/@username)" } } }arguments 14 linespostcopilot_export_following reads unknown never probed
Export up to 60 accounts that a Threads user follows. Returns usernames, display names, follower counts, and verification status. Provide a profile URL like https://www.threads.com/@username.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "url" ], "properties": { "url": { "type": "string", "format": "uri", "description": "The Threads profile URL (e.g. https://www.threads.com/@username)" } } }arguments 14 linespostcopilot_read_guide reads unknown never probed
Read a PostCopilot blog post / guide about Threads. Returns the full text content. Use postcopilot://blog/catalog resource first to see available guides, or provide a topic to search.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "topic" ], "properties": { "topic": { "type": "string", "description": "Topic to search for (e.g. \"viral\", \"video download\", \"export followers\", \"analytics\") or a blog slug" } } }arguments 13 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 idc0d87b60a25766fa.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/c0d87b60a25766fa/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/c0d87b60a25766fa?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.