The Poliety
NPM · POLIETY-MCP · SCANNED AUG 20
AI news for agents: editions, change feeds, integrity proofs, and governed events with evidence.
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 →
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 8 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 Management33
- Stability observed for 10 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
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · poliety-mcp
claude mcp add dburks-svg-poliety -- npx -y poliety-mcp
codex mcp add dburks-svg-poliety -- npx -y poliety-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dburks-svg-poliety": {
"type": "local",
"command": [
"npx",
"-y",
"poliety-mcp"
],
"enabled": true
}
}
} openclaw mcp add dburks-svg-poliety --command npx --arg -y --arg poliety-mcp
mcp_servers:
dburks-svg-poliety:
command: "npx"
args: ["-y", "poliety-mcp"] {
"mcpServers": {
"dburks-svg-poliety": {
"command": "npx",
"args": [
"-y",
"poliety-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.
- 19 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Aug 26 +16
- Malware scan: unverified → pass ▲ security
- Schema quality: pass → fail ▼ functional
- Package version: 1.2.0 → 1.3.0 functional
- 11 Aug 26 −13
- Malware scan: pass → unverified ▼ security
- Schema quality: 94 → 111 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → excellent functional
- Package version: 1.0.0 → 1.2.0 functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 58
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 20 Aug 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 |
Dependencies 5 packages
| Packages resolved | 5 |
|---|---|
| Stale | 3 |
| Tree resolution | Complete |
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.
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.