Political Comms MCP server
Which servers in the official MCP registry are Political Comms's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-19
- Registry namecom.politicalcomms/docsverified in the MCP registry
The registry name sits under politicalcomms.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-19
- Tools3
- Server calls itselfPolitical Comms
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 250 ms.
- Answeredmeasuring2 of the 7 daily checks it takes to print a share
- Median first answer335 ms
- Space in an agent's context≈ 1,277 tokensthe definitions of all its tools (3), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Every tool passes all six checks.
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The state of vendors' MCP servers: method and numbers →
search_political_commsSearch across the Political Comms knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Political Comms, find specific documentation, understand how…
query_docs_filesystem_political_commsRun a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Political Comms documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing runs on the user's…
submit_feedbackReport a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"docs": {
"type": "http",
"url": "https://docs.politicalcomms.com/mcp"
}
}
}- com.politicalcomms/apinot asked yetverified in the MCP registry
OpenAPI spec
49 paths, read 2026-10-19. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.