ToolsMCP
Quibbly
Listed in the official MCP Registry with a hosted streamable-http endpoint. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- quibbly.co
- Prerequisites
- An MCP client that supports streamable-http. No credential header is declared in the registry record.
- Current version
- 1.1.0 · updated
- Official links
Publisher’s description
Your LinkedIn inbox, connections and video views for AI. Works with any CRM. Drafts only.
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 remote endpoint (streamable-http)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- quibbly.co
- Version observed
- 1.1.0
- Source
- registry.modelcontextprotocol.io/v0.1/servers/co.quibbly%2Flinkedin-inbox/versions/1.1.0
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Read, draft and send email | Publisher description mentions “inbox”, “drafts”. | No connection check or task run. Capability is as described by the publisher. | Rule email matched: “inbox”, “drafts”. Rule email. |
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
- Remote endpoints
https://server.quibbly.co/mcp(streamable-http)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
co.quibbly/linkedin-inbox
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.