The Poliety
NPM · POLIETY-MCP
AI news for agents: editions, change feeds, integrity proofs, and governed events with evidence.
Available components
Last scanned (9 hours ago)
Scores higher than 46% of npm 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 Security96
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 3 of 5 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 85 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 813 tokens (~116/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 −3
- Stability: pass → 0.80 functional
- 30 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 26 0
- Stability: pass → 0.97 functional
- 23 Oct 26 0
- Stability: 0.97 → pass security
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 −1
- Stability: pass → 0.93 functional
- 17 Oct 26 +3
- Stability: 0.77 → pass security
- 16 Oct 26 −3
- Stability: pass → 0.77 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 5 Nov 2026 · Analysed npm/poliety-mcp@1.3.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 5 packages
| Packages resolved | 5 |
|---|---|
| Stale | 3 |
| 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 →
poliety_ask ~130
Ask The Poliety's concierge a question about the service itself: coverage (what dates the archive holds), capabilities (endpoints, integrity verification, tools), and tiers (what is free, what the key buys). Answers are grounded in Poliety's published docs and are non-canonical; the canonical_urls field in the response lists the citable sources. Not for news content (use poliety_latest or poliety_changes). No API key required; a key raises the rate limit.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | A plain-language question about The Poliety service, up to 2000 characters. |
No output schema declared.
No examples provided.
poliety_changes ~187
Get what changed since your last check: new stories, score changes, corrections. Pass the cursor from a previous response to receive only new changes, or use 'since' with an ISO 8601 timestamp. On first call with no cursor or since, returns a starting cursor for future delta queries.
| Name | Type | Req | Description |
|---|---|---|---|
| change | string | – | Filter by change type. |
| cursor | string | – | Opaque cursor from a previous poliety_changes response. |
| kind | string | – | Filter to wire items or editorial briefs. |
| limit | integer | – | Maximum results (default 200). |
| minScore | number | – | Minimum score threshold (wire items are scored 0-100). |
| section | string | – | Filter to a section (e.g. 'ai', 'startups'). |
| since | string | – | ISO 8601 timestamp. Alternative to cursor; returns changes since this time. |
No output schema declared.
No examples provided.
poliety_event_evidence ~103
Inspect one event's full evidence package to decide whether it is trustworthy enough to act on: epistemic status and confidence with rationale, sources by authority, the complete Bench tribunal receipt (verdict, constitution hash, challenger findings, defender rebuttals, oracle reasoning), integrity hashes with links to the free published files, and full provenance. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | The evt_ id of the event, from poliety_events. |
No output schema declared.
No examples provided.
poliety_event_history ~84
Get one event's supersession lineage, oldest first: what was believed at each point, at what confidence, and what corrected it. Later entries supersede, never overwrite, so the record of an earlier belief survives its correction. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | The evt_ id of any event in the lineage, from poliety_events. |
No output schema declared.
No examples provided.
poliety_events ~182
Get canonical events: governed, provenance-backed, hash-chained records of material changes in the AI and software ecosystem (status transitions, SDK releases, pricing and spec changes). Pass the next_cursor from a previous response as 'since' to receive only newer events. No API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | – | Filter by entity id (e.g. 'anthropic', 'openai', 'nodejs'). |
| limit | integer | – | Maximum results (default 100). |
| min_materiality | number | – | Only events at or above this materiality (0 to 1). |
| since | string | – | Opaque cursor from a previous poliety_events response; omit to walk from the start of the chain. |
| type | string | – | Filter by event type (e.g. 'sdk.released', 'status.degraded', 'pricing.changed'). |
No output schema declared.
No examples provided.
poliety_integrity ~59
Verify The Poliety's integrity chain: an append-only hash chain proving past editions have not been rewritten. Returns the chain head, root, length, and a witness recipe you can run to independently verify the current edition. No API key required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
poliety_latest ~68
Get today's AI news briefing from The Poliety: the lead story, briefs, and scored wire items. Returns the current edition as structured JSON. No API key required: without one this reads the free public edition; with one it reads the paid API's copy enriched with firstSeenAt timestamps.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the The Poliety MCP server?
The Poliety runs locally as an npm package, launched with npx -y poliety-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · poliety-mcp
claude mcp add dburks-svg-poliety -- npx -y poliety-mcp
What is the The Poliety MCP server?
The Poliety is an MCP server listed in the public MCP registry as io.github.dburks-svg/poliety. AI news for agents: editions, change feeds, integrity proofs, and governed events with evidence. This page covers its npm package (poliety-mcp).
Is the The Poliety MCP server safe to use?
The Poliety scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 The Poliety MCP server expose?
The Poliety exposes 7 tools: poliety_latest, poliety_changes, poliety_integrity, poliety_events, poliety_event_evidence, and 2 more. Their descriptions and schemas cost roughly 813 tokens of context every time the server is loaded.
Is the The Poliety MCP server still maintained?
The Poliety is still listed as active in the MCP registry. We last reached this channel on 5 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 The Poliety MCP server under?
The Poliety declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the The Poliety MCP server?
VerifyMCP ran 15 checks on The Poliety, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about The Poliety: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.