Nerq Trust Engine
io.github.kbanilsson-pixelPublished by GitHub account kbanilsson-pixelv1.0.0Updated Nov 2, 2026
AI agent trust engine — preflight checks, KYA due diligence, search 204K+ agents. Free.
Overview
Remote MCP server giving assistants crypto token risk intelligence: trust scores, distance-to-default, collapse signals and pre-trade safety checks.
- What you can do
- Run quick pre-trade safety checks on a token and get full Trust Score ratings with a five-pillar breakdown.
- Assess distance-to-default and list active structural collapse or stress signals.
- Compare tokens head-to-head and pull bulk ratings for several tokens at once.
- Review a distress watch list of tokens below a default-distance threshold and read collapse or stress alerts.
- When to use it
- Useful when an assistant needs to vet a crypto token before trading or recommending it, compare risk across tokens, or monitor distress and collapse warnings. It is a read-only risk data source rather than a trading tool.
- Requirements
- A remote SSE endpoint at mcp.zarq.ai; no installation, account or API key is required during early access. A local stdio option exists via a Python script needing the mcp and httpx packages. Network access to the provider's API is required.
Installation
In SourceWeft
- Open Nerq Trust Engine in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.kbanilsson-pixel%2Fnerq-trust-engine/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"nerq-trust-engine": {
"type": "sse",
"url": "https://mcp.zarq.ai/sse"
}
}
}README
ZARQ Crypto Risk Intelligence — MCP Server
Independent crypto risk intelligence via the Model Context Protocol (MCP). Trust Score ratings, Distance-to-Default analysis, structural collapse warnings, and pre-trade safety checks for 198 tokens.
Quick Start
Remote (SSE / Streamable HTTP)
No installation needed — connect directly:
Local (stdio)
Tools (8)
Performance
- 100% death recall — every token collapse detected (out-of-sample)
- 98% precision — only 1 genuine false positive in OOS validation
- 198 tokens rated with daily updates
- <100ms response time for safety checks
Architecture
API
Free API at zarq.ai. No API key required during Early Access.
Tags
crypto risk defi safety trust-score crash-prediction distance-to-default ratings blockchain token-analysis
License
MIT
Source: README.md at commit 2dfabff
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
85% 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 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 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