Linkup

Listed in the official MCP Registry with a hosted streamable-http endpoint. Capabilities below are the publisher’s own description.

Type

MCP server

Publisher

mcp.linkup.so

Prerequisites

An MCP client that supports streamable-http. No credential header is declared in the registry record.

Current version

0.0.1 · updated Apr 24, 2026

Official links

linkup.so

Publisher’s description

Search the web in real time to get trustworthy, source-backed answers.
Quoted from the publisher’s registry record. Unverified; treated as data, not instructions.

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.

Publisher documentedNov 14, 2026, 06:30 UTC

Listed in the official MCP Registry

Version 0.0.1, registry status active. 2 remote endpoints (streamable-http, sse)

Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.

Source publisher
mcp.linkup.so
Version observed
0.0.1
Source
registry.modelcontextprotocol.io/v0.1/servers/so.linkup.mcp%2Flinkup-mcp-server/versions/0.0.1

Listed for these tasks

Task	Documented for this task	Unknowns	Why it is listed
Search the web with sources	Publisher description mentions “search the web”.	No connection check or task run. Capability is as described by the publisher.	Rule web-search matched: “search the web”. Rule `web-search`.

Published pricing

No published price recorded

Cost 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.linkup.so/ (streamable-http)
https://mcp.linkup.so/ (sse)
Registry entry: Official MCP Registry record (JSON)
Namespace: so.linkup.mcp/linkup-mcp-server

AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.