ToolsMCP
Linked API
Listed in the official MCP Registry with a hosted streamable-http endpoint and an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- linked-api (GitHub)
- Prerequisites
- An MCP client that supports streamable-http. The publisher declares a required credential header. Install @linkedapi/mcp from npm (stdio transport). Declares 2 secret inputs. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 2.3.21 · updated
- Official links
Publisher’s description
Manage LinkedIn messages, connections, posts, and profile data through Linked API.
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 2.3.21, registry status active. 1 remote endpoint (streamable-http); 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- linked-api (GitHub)
- Version observed
- 2.3.21
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.Linked-API%2Flinkedapi-mcp/versions/2.3.21
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Draft and publish social media posts | Publisher description mentions “linkedin”, “posts”. | No connection check or task run. Capability is as described by the publisher. | Rule social-posts matched: “linkedin”, “posts”. 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
- Remote endpoints
https://mcp.linkedapi.io/mcp(streamable-http, declares a required credential)- Packages
@linkedapi/mcp(npm, stdio, 2 secret inputs)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.Linked-API/linkedapi-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.