Neglect MCP Server

by neglect Your server? Claim it

answering

Neglect is answering right now. Last checked 11 min ago. Last commit 18 Nov 2025.

Full Solana DeFi coverage: launchpads, tokens, trades, and wallets, decoded at scale.

Uptime history 91 days of history · worst day 0%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

144 ms

Response time

average over 24h

Stars

last commit 18 Nov 2025

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 August 2026. No other catalogue keeps this.

9 Aug the owner changed

Nothing serious here today

Today is the operative word: we check Neglect every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp-server --transport http https://api.neglect.trade/mcp

Settings → Connectors → Add custom connector, then paste this address

https://api.neglect.trade/mcp

~/.codex/config.toml

[mcp_servers.mcp-server]
url = "https://api.neglect.trade/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp-server": {
      "url": "https://api.neglect.trade/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "mcp-server": {
      "type": "http",
      "url": "https://api.neglect.trade/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URL	Transport	State	Latency	Checked
https://api.neglect.trade/mcp	streamable-http	needs auth	114 ms	11 min ago

Alternatives to Neglect

same job, measured the same way

Gapproof

by cloudcorprecords

Find untested functions: link tests to code, score coverage, record proven runs locally.

275 installs/wk local only

Test Coverage MCP

by goldbergyoni

Analyze test coverage from LCOV files - makes AI agents coverage-aware without wasting tokens

62 installs/wk local only

Scry MCP

by pfeilisolana

Keyless MCP bridge to Scry Solana wallet intel: free coverage check, catalog, x402 paid endpoints.

101 installs/wk local only

Analyst Ratings

by pipeworx-io

Analyst Ratings — today's US stock analyst upgrades, downgrades, coverage initiations and…

471 installs/wk 46 tools answering

Yandex Tracker

by sdamarketing

MCP server for Yandex Tracker: full API v3 coverage (187 tools)

69 installs/wk local only

Resend Email MCP

by helbertparanhos

Complete Resend email MCP: full API coverage + debug layer (deliverability, DNS, bounces).

52 installs/wk local only

Test Intel

by barissozudogru

Coverage analysis, untested function detection and complexity scoring for TS and JS.

51 installs/wk local only

Kai

by kailayerhq

Semantic code intelligence — call graphs, dependencies, impact analysis, and test coverage.

252 installs/wk local only

Neglect — questions

Answers built from our own checks of this server.

Why is there no tool list for Neglect?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Neglect working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 144 ms. The bar chart above shows every period we have measured.

How do I connect Neglect?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.

Does Neglect need an API key?

Yes. Every time we knock, Neglect answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Neglect?

It answers our handshake in 144 ms on average, which is faster than 87% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Neglect open source?

We cannot say either way: 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.