The Neural Ledger Intelligence runs on your own machine — the client starts it, so there is no endpoint to ping. 37 installs a week from npm. Last commit 21 Oct 2026.
Read-only global event and evidence intelligence with entities, assets, and impact paths.
We read the source, 1 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
COPY package.json package-lock.json .npmrc tsconfig.base.json ./
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
--volume /var/run/docker.sock:/var/run/docker.sock \
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add intelligence -e 'TNL_API_KEY=<TNL_API_KEY>' -- npx -y @theneuralledger/mcp
{
"mcpServers": {
"intelligence": {
"command": "npx",
"args": [
"-y",
"@theneuralledger/mcp"
],
"env": {
"TNL_API_KEY": "<TNL_API_KEY>"
}
}
}
}
[mcp_servers.intelligence]
command = "npx"
args = ["-y", "@theneuralledger/mcp"]
env = { TNL_API_KEY = "<TNL_API_KEY>" }
{
"mcpServers": {
"intelligence": {
"command": "npx",
"args": [
"-y",
"@theneuralledger/mcp"
],
"env": {
"TNL_API_KEY": "<TNL_API_KEY>"
}
}
}
}
{
"servers": {
"intelligence": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@theneuralledger/mcp"
],
"env": {
"TNL_API_KEY": "<TNL_API_KEY>"
}
}
}
}
Put your own value in place of
<TNL_API_KEY> (The Neural Ledger member API key).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
TNL_BASE_URL (Optional TNL API base URL).
One Data Plane for crypto research, with 42 live tools for markets, entities, news, and signals.
Read-only agent identity index with provenance, historical evidence and explained coverage.
Research intelligence for AI coding agents. 2M+ CS papers with evidence and tradeoffs.
Live geopolitical and markets intelligence wire: 35k+ wire items, event threads, 55k+ articles.
Local, evidence-based application security assessment with an evidence ledger and retests.
Local-first grocery price intelligence with a read-only MCP server.
Local read-only MCP scanner for known prompt-injection patterns with exact evidence and no network.
Evaluate an MCP server with passmcp and verify its attestations, from inside the agent. Read-only.
Answers built from our own checks of this server.