Home / MCP registry index / xyz.urbangametheory/urban-game-theory

Urban Game Theory — Consensus Builder

xyz.urbangametheory/urban-game-theory in the official MCP registry. Endpoint https://urbangametheory.xyz/mcp. Source: github.com/Poglavar/consensus-builder.

The registry describes it as: Inspect real parcels, create and edit urban plans, compare alternatives, and share 2D/3D designs.

We read its 46 tools on 2026-10-31. 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.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code
claude mcp add --transport http urban-game-theory https://urbangametheory.xyz/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "urban-game-theory": {
      "url": "https://urbangametheory.xyz/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"urban-game-theory","type":"http","url":"https://urbangametheory.xyz/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard
claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

ugt_capabilities ugt_activity ugt_list_agreements ugt_get_agreement ugt_list_attesters ugt_support_status ugt_oracle_events ugt_inspect_verified_fact ugt_publish_design ugt_propose_agreement ugt_voting_status ugt_cast_community_vote ugt_approval_link ugt_find_place ugt_parcel_context ugt_list_designs ugt_get_design ugt_markets ugt_explain ugt_draft_road ugt_draft_building ugt_draft_track ugt_draft_station ugt_draft_space ugt_draft_parcel_layout ugt_draft_urban_rule ugt_modify_design ugt_inspect_design ugt_edit_design ugt_compare ugt_draft_agreement ugt_inspect_agreement ugt_edit_agreement ugt_draft_plan ugt_get_plan ugt_validate_plan ugt_inspect_plan ugt_edit_plan ugt_publish_plan ugt_help ugt_list_sources ugt_export_draft ugt_import_design ugt_import_model ugt_render_preview ugt_submit_feedback

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): c774b600c1e389b5. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/xyz-urbangametheory-urban-game-theory/badge.svg)](https://lazaretto.dev/mcp-registry/xyz-urbangametheory-urban-game-theory)

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.