ToolsMCP
Postlint MCP Server
Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- conorbronsdon (GitHub)
- Prerequisites
- Install @conorbronsdon/postlint-mcp from npm (stdio transport). Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 1.1.0 · updated
- Official links
Publisher’s description
Check a social post against a platform's real character limit: X, Bluesky, LinkedIn, Threads.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 1.1.0, registry status active. 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- conorbronsdon (GitHub)
- Version observed
- 1.1.0
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.conorbronsdon%2Fpostlint-mcp/versions/1.1.0
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Draft and publish social media posts | Publisher description mentions “bluesky”, “linkedin”, “post”. | No connection check or task run. Capability is as described by the publisher. | Rule social-posts matched: “bluesky”, “linkedin”, “post”. Rule social-posts. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
@conorbronsdon/postlint-mcp(npm, stdio)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.conorbronsdon/postlint-mcp
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.