VerdictSwarm MCP
PYPI · VERDICTSWARM-MCP · SCANNED SEP 20
Read-only pre-trade token risk verdicts and size-aware Solana exit screening for agents.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 48 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability41
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 160 tokens (~32/item across 5 items; 3 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the VerdictSwarm MCP server?
VerdictSwarm MCP runs locally as a PyPI package, launched with uvx verdictswarm-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · verdictswarm-mcp
claude mcp add sentien-labs-verdictswarm-mcp -- uvx verdictswarm-mcp
{
"mcpServers": {
"sentien-labs-verdictswarm-mcp": {
"command": "uvx",
"args": [
"verdictswarm-mcp"
]
}
}
} {
"servers": {
"sentien-labs-verdictswarm-mcp": {
"command": "uvx",
"args": [
"verdictswarm-mcp"
]
}
}
} codex mcp add sentien-labs-verdictswarm-mcp -- uvx verdictswarm-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sentien-labs-verdictswarm-mcp": {
"type": "local",
"command": [
"uvx",
"verdictswarm-mcp"
],
"enabled": true
}
}
} openclaw mcp add sentien-labs-verdictswarm-mcp --command uvx --arg verdictswarm-mcp
mcp_servers:
sentien-labs-verdictswarm-mcp:
command: "uvx"
args: ["verdictswarm-mcp"] {
"McpServers": {
"sentien-labs-verdictswarm-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"verdictswarm-mcp"
]
}
}
} assistant mcp add sentien-labs-verdictswarm-mcp -t stdio -c uvx -a verdictswarm-mcp
{
"mcpServers": {
"sentien-labs-verdictswarm-mcp": {
"command": "uvx",
"args": [
"verdictswarm-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −2
- Stability: pass → 0.80 functional
- 17 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 16 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 15 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 14 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −2
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/verdictswarm-mcp@0.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_token ~65
Return a v2 verdict summary with action, score, and strongest signals on the free tier.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Token contract or mint address |
| chain | string | – | Blockchain network |
| level | string | – | Verdict depth: triage, fast, or deep |
Structured output declared, but exposes no named fields.
No examples provided.
exit_sim ~59
Screen a proposed Solana trade size against exit risk caps on the free tier.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Solana token mint address |
| side | string | yes | Proposed trade side |
| size_usd | number | yes | Trade size in USD |
Structured output declared, but exposes no named fields.
No examples provided.
get_pricing ~26
Return live free-tier levels, quotas, and pricing from the v2 discovery endpoint.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
What is the VerdictSwarm MCP server?
VerdictSwarm MCP is listed in the public MCP registry as io.github.sentien-labs/verdictswarm-mcp. Read-only pre-trade token risk verdicts and size-aware Solana exit screening for agents. This page covers its PyPI package (verdictswarm-mcp).
Is the VerdictSwarm MCP server safe to use?
VerdictSwarm MCP scores 60 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the VerdictSwarm MCP server expose?
VerdictSwarm MCP exposes 3 tools: check_token, exit_sim, get_pricing. Their descriptions and schemas cost roughly 150 tokens of context every time the server is loaded.
Is the VerdictSwarm MCP server still maintained?
VerdictSwarm MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.