io.github.sravanism/esrp-mcp-server-test
io.github.sravanism/esrp-mcp-server-test
Is the io.github.sravanism/esrp-mcp-server-test MCP server down? Yes. It has given no valid answer since 2026-10-16: not found.
The Microsoft OSS MCP server exposes tools to discover & validate trusted Microsoft OSS Packages.
not found down since 2026-10-16 · probed 2026-11-15 · unchanged since 2026-10-30
npm error notarget In most cases you or one of your dependencies are requesting npm error notarget a package version that doesn't exist. npm error A complete lo
- Run it
- npx -y esrpmicrosoft-oss-mcp-test@1.0.1 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/sravanism/esrp-mcp-server
- Registry
- active, updated 2025-12-18 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.spronta/mcp · alive
- io.github.spuentesp/lain · needs network
- zoanthrope io.github.spuentesp/zoanthrope · needs network
- io.github.sqemo/sqemo · alive
- io.github.srbryant86/mcp-server · alive
- io.github.srbsa/diffgate · alive
- TablaFocusMCP io.github.sreeramkongeseri/tablafocus-mcp · alive
- Kosha Model Discovery io.github.sriinnu/kosha-discovery · crashed on start
Servers that mention esrp or microsoft or discover.
- com.microsoft.esrp/esrp-oss-mcp-test · no DNS
- com.microsoft/esrp-oss-mcp-test · no DNS
- adplane ai.adplane/google-ads · needs auth
- ai.adoraads/beauty · alive
- AFMR Discovery ai.afmr/discovery · alive
- ai.astrofabric/mcp · not found
- Boolsai Grep ai.boolsai/grep · no DNS
- Orbit ai.buildwithorbit/orbit · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-16, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.