The Poliety

io.github.dburks-svgPublished by GitHub account dburks-svgv1.3.0Updated Oct 24, 2026

AI news for agents: editions, change feeds, integrity proofs, and governed events with evidence.

VerifiedSTDIODesktop onlyWeb Search & Scraping

Server details

Identifier: io.github.dburks-svg/poliety
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account dburks-svg for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.dburks-svg%2Fpoliety.svg)](https://sourceweft.com/mcp/io.github.dburks-svg%2Fpoliety?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server that gives an assistant access to Poliety's AI news editions, change feeds, integrity proofs, and governed events with evidence.

What you can do: The Poliety MCP server exposes tools for retrieving AI news content: poliety_latest for current editions, poliety_changes for change feeds, poliety_integrity for integrity proofs, poliety_events and poliety_event_history for governed events, poliety_event_evidence for supporting evidence, and poliety_ask for querying. Some tools work without authentication, while others require an API key. It runs locally over stdio and is intended for desktop use.
When to use it: Use it when an assistant needs to pull AI news, track changes, verify integrity, or work with governed events and their evidence. It is suited to research, monitoring, or reporting workflows that depend on Poliety's curated feeds.
Requirements: Runs as a local process via npx (npm package poliety-mcp). Requires Node.js. An API key is needed for poliety_changes, poliety_event_evidence, and poliety_event_history, supplied through the POLIETY_API_KEY environment variable; other tools work without a key. Desktop only; network access to poliety.com is required.

Before you install

The POLIETY_API_KEY secret is required for some tools and should be kept confidential. The server sends requests to poliety.com, so news queries and any data included in them leave the local machine. No write, payment, or wallet actions are described.

Installation

In SourceWeft

Open The Poliety in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.3.0LatestSep 16, 2026

Score

25% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.