mcp server
Linkup
Search the web in real time to get trustworthy, source-backed answers.
Description as published by the maintainer. Source
- version 0.0.1
- slowing
- retrieval
slowing — Registry entry last updated 2026-04-24. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
The endpoint answered, but not with a valid Model Context Protocol response (initialize rejected: MCP error -32603: Invalid response format).
Endpoint status observed on . Source: https://mcp.linkup.so.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.0.1 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-04-24 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-04-24 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp endpoint status | protocol_error | The endpoint answered, but not with a valid Model Context Protocol response (initialize rejected: MCP error -32603: Invalid response format). | as of probe | mcp.linkup.so |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json