The Neural Ledger Intelligence
com.theneuralledgerPublished by theneuralledger.comv0.1.0Updated Nov 3, 2026
Read-only global event and evidence intelligence with entities, assets, and impact paths.
Overview
Read-only MCP server for The Neural Ledger, giving an assistant news search, entity and asset intelligence, impact paths, and event explanations.
- What you can do
- Search news and events across The Neural Ledger's intelligence API
- Look up entities, assets and impact paths, and get explanations of events
- Run Ledger AI deep research when a research runner is configured
- Check service status
- Optionally expose a research workspace resource for the scoped research tools
- When to use it
- Useful when an assistant needs read-only global event and evidence context — news search, entity or asset relationships, and impact analysis — rather than raw market data. It suits research and briefing workflows where the Ledger's curated intelligence is the source.
- Requirements
- Runs locally over stdio via the npm package, typically with npx. Requires a Neural Ledger member API key supplied as TNL_API_KEY, or as a bearer token for HTTP mode. Optional TNL_BASE_URL, TNL_MCP_HOST and TNL_MCP_PORT settings; HTTP mode binds to loopback by default. Network access to the TNL API is needed.
Installation
In SourceWeft
- Open The Neural Ledger Intelligence in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@theneuralledger/mcp
Read-only Model Context Protocol server for The Neural Ledger event and evidence intelligence API.
Stdio
Streamable HTTP
The server binds to 127.0.0.1:7317 by default. Override it with TNL_MCP_HOST and TNL_MCP_PORT. HTTP clients may send their TNL key as Authorization: Bearer ...; it is forwarded only to the TNL API and is never included in tool output.
HTTP mode requires a bearer key even when TNL_API_KEY is present in the server environment. A loopback-only single-user deployment can explicitly restore environment-key fallback with TNL_MCP_ALLOW_ENV_API_KEY=1; do not enable that mode on a shared or remotely reachable server.
The tools expose news search, asset/entity/impact-path intelligence, event explanation, Ledger AI deep research, and service status. TNL provides event and evidence intelligence; its market quotes are display context rather than an execution-grade price feed.
When configured with a TnlResearchRunner, the server also exposes six scoped
tnl_research_* tools plus the ui://tnl/research-workspace MCP App resource.
Without that runner, research tools are not advertised. Hosted callers must hold
the tnl:research scope in addition to base read access.
Source: packages/mcp/README.md at commit 23034e3
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts