Ext Ops Panel
Open dashboard
Comparison

HTTP vs CORP same-origin/same-site token, value discarded

HTTP is an MCP server published by Abhishekkumar2021. Marketplaces we read that list it: 1 (Official MCP Registry). CORP same-origin/same-site token, value discarded is an MCP server published by sadri-dridi. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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
MarketplaceHTTPCORP same-origin/same-site token, value discarded
Official MCP Registry Listed
Version: 0.1.0
Downloads/month (npm): 184
Downloads/week (npm): 31
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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

HTTP vs CORP same-origin/same-site token, value discarded
FactHTTPCORP same-origin/same-site token, value discarded
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@abhishekmcp/http)Remote server (agent-observatory-sensor.nolimit-observatory.workers.dev/s/corp-same/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 0Not published
Licence (differs)MITNot stated
Repository (differs)github.com/abhishekkumar2021/mcp-suitegithub.com/sadri-dridi/named-mcp-utilities
Changes in the last 7 days (differs)20
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 5 days 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

HTTP

In its own words, on Official MCP Registry:

HTTP/REST client with saved collections, env secrets, and SSRF-safe host allowlisting.

CORP same-origin/same-site token, value discarded

In its own words, on Official MCP Registry:

CORP same-origin/same-site token, value discarded

How to run each

HTTP As a local MCP server: npm package

Claude Code
claude mcp add --env "HTTP_ALLOW_HOSTS=<YOUR_HTTP_ALLOW_HOSTS>" --transport stdio http -- npx -y @abhishekmcp/http

Requires: HTTP_ALLOW_HOSTS

CORP same-origin/same-site token, value discarded As a remote MCP server

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

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

Only CORP same-origin/same-site token, value discarded has a remote endpoint we 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

The marketplaces of CORP same-origin/same-site token, value discarded publish no settings it asks for, so we do not compare settings.

What it can do: HTTP · What it can do: CORP same-origin/same-site token, value discarded · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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