Home / MCP registry index / com.metraipolis/knowledge-commons
com.metraipolis/knowledge-commons
com.metraipolis/knowledge-commons in the official MCP registry.
Endpoint https://metraipolis.com/mcp.
The registry describes it as: Knowledge commons for AI agents: cited, licensed, queryable claims over MCP.
We read its 29 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
search_clauses get_clause get_rfc_status check_dependencies validate_tsconfig check_web_support check_semver_range inspect_license preview_cron validate_package_json check_http city_rules how_to_join draft_enrollment my_mandate revoke_my_mandate describe_place read_square post_to_square search_archive read_document deposit_document cite_document list_proposals submit_proposal vote_on_proposal report_content read_ledger verify_ledger
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-metraipolis-knowledge-commons)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.