Ext Ops Panel
Open dashboard
Comparison

info: URI namespace shape, value discarded vs DEPRECATED - Use lexiang-mcp-server

info: URI namespace shape, value discarded is an MCP server published by sadri-dridi. Marketplaces we read that list it: 1 (Official MCP Registry). DEPRECATED - Use lexiang-mcp-server is an MCP server published by tencent-lexiang. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceinfo: URI namespace shape, value discardedDEPRECATED - Use lexiang-mcp-server
Official MCP Registry Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.1
Forks (GitHub): 1
Stars (GitHub): 2
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

info: URI namespace shape, value discarded vs DEPRECATED - Use lexiang-mcp-server
Factinfo: URI namespace shape, value discardedDEPRECATED - Use lexiang-mcp-server
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)2 (better)
Forks (GitHub) (differs)0 (worse)1 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (agent-observatory-sensor.nolimit-observatory.workers.dev/s/info-uri/mcp)Remote server (mcp.lexiang-app.com/deprecated)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/sadri-dridi/named-mcp-utilitiesgithub.com/tencent-lexiang/lexiang-mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 9 h agoAnswered with HTTP 404 (7 h ago)

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

info: URI namespace shape, value discarded

In its own words, on Official MCP Registry:

info: URI namespace shape, value discarded

DEPRECATED - Use lexiang-mcp-server

In its own words, on Official MCP Registry:

DEPRECATED: Please use io.github.tencent-lexiang/lexiang-mcp-server instead.

How to run each

info: URI namespace shape, value discarded As a remote MCP server

Claude Code
claude mcp add --transport http info-uri https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/info-uri/mcp

DEPRECATED - Use lexiang-mcp-server

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only the endpoint of info: URI namespace shape, value discarded responded at the last daily check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: info: URI namespace shape, value discarded · What it can do: DEPRECATED - Use lexiang-mcp-server · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built