Verum Signal
PYPI · VERUMSIGNAL-MCP
Political debate claims from Verum Signal: who said each one and how it was rated.
Available components
Last scanned (22 hours ago)
Scores higher than 64% of PyPI servers
Category News and Social
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 9 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 412 tokens (~103/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 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
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 26 Oct 26 53
First indexed and scored.
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 4 Nov 2026 · Analysed pypi/verumsignal-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
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 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
get_api_status ~53
Get Verum Signal corpus statistics: total articles, total claims, and how many carry a verdict. Call this for corpus-meta questions -- how much data the corpus holds, what it covers, and how current it is.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_debate_verdicts ~110
Get ALL rated claims from a political debate. Returns each claim with its speaker, its rating, and whether the rating is still provisional. Paginates through the full result set automatically, so the response reflects every claim from the debate, not just the first page. Use this for claims made during a specific debate.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Debate slug, e.g. 'colorado-gov-rep-2026-r3'. Use list_debates to find slugs. |
No output schema declared.
No examples provided.
list_debates ~20
List available political debates with claim counts and status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_recent_claims ~229
Search and list claims from Verum Signal's corpus. Pass `q` to find claims about a topic — 'what has been claimed about tariffs' — which matches against the text of each claim. Without `q` it returns claims in recency order, most recent first. Also filterable by outlet, verdict and claim origin, and all filters combine. Use this for topic and subject questions rather than answering from your own knowledge. Returns claims reported by news outlets, each with its rating. Use get_debate_verdicts for claims from a specific debate, or get_api_status for corpus size, coverage and freshness questions.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of results (1-50, default 10) |
| outlet | string | – | Filter by outlet domain, e.g. foxnews.com |
| q | string | – | Find claims whose text contains this term, case-insensitive. Use for topic questions, e.g. 'tariffs' or 'immigration'. |
| verdict | string | – | Filter by verdict: supported, disputed, overstated, not_supported, etc. |
No output schema declared.
No examples provided.
How do I install the Verum Signal MCP server?
Verum Signal runs locally as a PyPI package, launched with uvx verumsignal-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 · verumsignal-mcp
claude mcp add brittbart-verumsignal-mcp -- uvx verumsignal-mcp
What is the Verum Signal MCP server?
Verum Signal is an MCP server listed in the public MCP registry as io.github.brittbart/verumsignal-mcp. Political debate claims from Verum Signal: who said each one and how it was rated. This page covers its PyPI package (verumsignal-mcp).
Is the Verum Signal MCP server safe to use?
Verum Signal scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 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 Verum Signal MCP server expose?
Verum Signal exposes 4 tools: list_recent_claims, get_debate_verdicts, list_debates, get_api_status. Their descriptions and schemas cost roughly 412 tokens of context every time the server is loaded.
Is the Verum Signal MCP server still maintained?
Verum Signal is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Verum Signal MCP server under?
Verum Signal declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.