Skip to content

MCP servers › xyz.urbangametheory › urban-game-theory

MCP server · registry snapshot 2026-10-24 · last tested 2026-10-24

xyz.urbangametheory/urban-game-theory

Inspect real parcels, create and edit urban plans, compare alternatives, and share 2D/3D designs. — the publisher's description

4 of 4 record checks metRead-only · tools listed 2026-10-24version 0.3.0JavaScriptstreamable HTTP30 tools

Summary

xyz.urbangametheory/urban-game-theory is a remote MCP server listed in the official MCP registry at version 0.3.0. On 2026-10-24 ProtocolProbe connected to it in read-only mode and read its inventory: 30 tools, 12 resources and 5 prompts.

Record checks

4 of 4 record checks met · 4 do not apply · 1 not checked

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not checked: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Sign-in
none needed to open a session
Repository
public
Tools
30
Last tested
2026-10-24

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-24
Mode
read-only (no tool calls)
Latest version
0.3.0, published 2026-10-24 (registry, as of the 2026-10-24 snapshot)
First listed version
2026-10-24 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-10-24
Package and repository
checked 2026-10-24
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-23, listed on 2026-10-24 with version 0.3.0 (published 2026-10-24).

Source: the official MCP Registry list on 2026-10-23 and on 2026-10-24.

What it is

What does this server offer?

Observed inventory
30tools
12resources
5prompts

None of its 30 tools are described as changing anything. For 30 the reading was uncertain, so no mark is shown.

  • ugt_capabilities

    “Read the live machine manifest (/docs/agents.json): the design and agreement JSON Schemas, endpoints, program ids, the oracle-fact x402 price and the tool list.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    Takes no inputs.

  • ugt_activity

    “Read the same activity stream used by the actor explorer for humans, algorithmic agents and LLM agents.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs
    • limitinteger
    • actorstring
    • sourcestring
    • actionstring
  • ugt_list_agreements

    “Read the agreement index (GET /agreements), newest first: each row has the agreement/v1 content, its design CIDs, input parcel ids, deadline, status and, once minted, its chain account (onchain).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs
    • citystring
    • designstring“Only agreements linking this design CID”
    • parcelstring“Only agreements taking this input parcel id”
    • limitinteger
  • ugt_get_agreement

    “Read an agreement from the index (GET /agreements/:cid) plus, when its content names a sponsor, its chain account (PDA of sponsor and CID) and that account as the chain holds it now (accountState: st…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • agreementCidstringrequired“Agreement CID (bafkrei…), as ugt_propose_agreement or ugt_list_agreements answers it”
  • ugt_list_attesters

    “Read the attester directory: lens members with kind and coverage.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input
    • kindstring“Only members of this kind, for example owner-consent”
  • ugt_support_status

    “Read on-chain donation escrow and soft-pledge totals for an agreement account (GET /agent/pledges/:account).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • agreementAccountstringrequired“Chain account of a minted (binding owners') agreement: the PDA ["agreement", sponsor, sha256(cid)] under the agreement program (ugt_get_agreement answers it)”
  • ugt_oracle_events

    “Read the source-hashed agreement_lifecycle events of an agreement account (executed, cancelled or expired), which its market settles on.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • agreementAccountstringrequired“Chain account of a minted (binding owners') agreement: the PDA ["agreement", sponsor, sha256(cid)] under the agreement program (ugt_get_agreement answers it)”
    • limitinteger
  • ugt_inspect_verified_fact

    “Fetch and decode the x402 challenge for an agreement's recipe-bound terminal fact without paying.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • agreementAccountstringrequired“Chain account of a minted (binding owners') agreement: the PDA ["agreement", sponsor, sha256(cid)] under the agreement program (ugt_get_agreement answers it)”
    • marketAccountstring
  • ugt_publish_design

    “Permanently publish public content: pin (POST /pins) and index (POST /designs) one design/v1 object; confirm=true required.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world yes

    3 inputs, 2 required
    • designobjectrequired“A design/v1 object exactly as the app publishes it: schema, goal, title, description, author, city, site, toleranceM, geometry, origin, authoredAt (each presen…”
    • parcelSourceIdstring“Parcel source to bind with; the city's default when absent”
    • confirmbooleanrequired“Explicitly authorize this write, paid or signed devnet action”
  • ugt_propose_agreement

    “Permanently publish public content: pin and index one agreement/v1 object (POST /pins, POST /agreements); confirm=true required.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world yes

    3 inputs, 2 required
    • agreementobjectrequired“An agreement/v1 object exactly as the app publishes it: schema, title, author, sponsor, city, createdAt, designs [{ cid, goal, title }], inputs { parcels, open…”
    • designsarray“Only unpublished linked designs to index with this agreement, such as parcel layouts.”
    • confirmbooleanrequired“Explicitly authorize this write, paid or signed devnet action”
  • ugt_approval_link

    “Build a wallet approval link.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs, 2 required
    • actionstringrequired
    • targetstringrequired
    • paramsobject
  • ugt_find_place

    “Find a place, address, parcel id or design title using the app search sources.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    5 inputs, 1 required
    • querystringrequired
    • citystring
    • parcelSourceIdstring
    • bboxarray
    • limitinteger
Show 18 more tools
  • ugt_parcel_context

    “Read one parcel or WGS84 point: source ground, area, planning sources and studies, buildings, nearby designs, agreements, markets and history.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    6 inputs, 1 required
    • citystringrequired
    • parcelSourceIdstring
    • parcelIdstring
    • pointarray
    • buildingSourceIdstring
    • planningSourceIdsarray
  • ugt_list_designs

    “List designs by city, WGS84 bbox or text.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs
    • citystring
    • bboxarray
    • qstring
    • limitinteger
  • ugt_get_design

    “Read a design by CID and return its map link.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • designCidstringrequired
  • ugt_markets

    “Read city contests, pools and devnet USDC stakes.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • citystringrequired
  • ugt_explain

    “Look up a term in the maintained domain vocabulary.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • termstringrequired
  • ugt_draft_road

    “Draft a road from WGS84 points or a street name/id with a small bbox and a cross-section.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    15 inputs, 1 required
    • citystringrequired
    • parcelSourceIdstring
    • parcelIdsarray
    • outlineobject
    • titlestring
    • descriptionstring
    • authorstring
    • authoredAtstring
    • pointsarray
    • streetstring
    • streetIdstring
    • bboxarray
    • presetstring
    • lanesarray
    • widthnumber
  • ugt_draft_building

    “Draft a parcel-bound building.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    14 inputs, 1 required
    • citystringrequired
    • parcelSourceIdstring
    • parcelIdsarray
    • outlineobject
    • titlestring
    • descriptionstring
    • authorstring
    • authoredAtstring
    • floorsinteger
    • heightnumber
    • usestring
    • coveragenumber
    • permittedboolean
    • planningSourcestring
  • ugt_draft_space

    “Draft a park, square or lake over parcel ids or an outline; no pin or index write.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    10 inputs, 2 required
    • citystringrequired
    • parcelSourceIdstring
    • parcelIdsarray
    • outlineobject
    • titlestring
    • descriptionstring
    • authorstring
    • authoredAtstring
    • spaceKindstringrequired
    • treeCountinteger
  • ugt_draft_parcel_layout

    “Draft automatic plots using the same equal-area or Schelling layout algorithm as the app.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    11 inputs, 1 required
    • citystringrequired
    • parcelSourceIdstring
    • parcelIdsarray
    • outlineobject
    • titlestring
    • descriptionstring
    • authorstring
    • authoredAtstring
    • algorithmstring
    • countinteger
    • plotLevelinteger
  • ugt_draft_urban_rule

    “Draft an authored urban rule.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    9 inputs, 2 required
    • citystringrequired
    • parcelSourceIdstring
    • parcelIdsarray
    • outlineobject
    • titlestring
    • descriptionstring
    • authorstring
    • authoredAtstring
    • ruleobjectrequired
  • ugt_modify_design

    “Fork a published CID, hosted draftRef or canonical draft with typed changes.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs, 2 required
    • designstring or objectrequired
    • changesarrayrequired
    • parcelSourceIdstring
  • ugt_inspect_design

    “Read exact authored JSON at JSON Pointer paths, including private drafts.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • designstring or objectrequired
    • pathsarray
  • ugt_edit_design

    “Atomically fork an exact design revision with JSON Patch add/replace/remove/test/copy/move, or geometry transform/union/difference/intersection/buffer at pointers.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs, 3 required
    • designstring or objectrequired
    • expectedCidstringrequired
    • editsarrayrequired
    • parcelSourceIdstring
  • ugt_compare

    “Compare canonical drafts, hosted draftRef references or indexed design/agreement CIDs.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs, 1 required
    • targetsarrayrequired
    • buildingSourceIdstring
    • parcelSourceIdstring
  • ugt_draft_agreement

    “Author the supplied roads as one connected network, then derive an agreement on isolated complete cadastral ground using the app formation handlers.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    13 inputs, 1 required
    • designsarrayrequired
    • rulePresetstring
    • rightsobject
    • lensstring
    • allocationsarray
    • moneyobject
    • currencystring
    • deadlinestring or null
    • sponsorstring or null
    • titlestring
    • authorstring
    • createdAtstring
    • parcelSourceIdstring
  • ugt_inspect_plan

    “Inventory an agreement plan by published CID/link, private draftRef or canonical agreement plus carried designs.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    5 inputs, 1 required
    • planstring or objectrequired
    • filterobject
    • includeGeometryboolean
    • offsetinteger
    • limitinteger
  • ugt_edit_plan

    “Create a private plan revision using granular add/remove/replace/edit operations on its designs, or convenient typed modify operations.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs, 2 required
    • planstring or objectrequired
    • expectedCidstringrequired
    • operationsarray
    • termsobject
  • ugt_submit_feedback

    “Submit to the private maintainer inbox and return a receipt ID.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    5 inputs, 2 required
    • kindstring
    • messagestringrequired
    • pageUrlstring
    • reportIdstring
    • confirmbooleanrequired

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-24.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
9% of 140
Tools with a description
100% of 30
Typical description length
293 characters

The tool set

Counted from the listing

Tools
30
Size of the list
about 13,360 tokens for an agent to load (characters ÷ 4)
Naming
30 of 30 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 30 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-24 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://urbangametheory.xyz/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "urban-game-theory": {
      "url": "https://urbangametheory.xyz/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "urban-game-theory": {
      "type": "http",
      "url": "https://urbangametheory.xyz/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"urban-game-theory","type":"http","url":"https://urbangametheory.xyz/mcp"}'
Claude Code
claude mcp add --transport http urban-game-theory https://urbangametheory.xyz/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://urbangametheory.xyz/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint urbangametheory.xyz/mcpSession openedmatchesour test · 2026-10-24
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-24
Repository github.com/Poglavar/consensus-builderOpens publiclymatchesapi.github.com · 2026-10-24

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
xyz.urbangametheory
GitHub owner
a personal account (Poglavar)
Repository
github.com/Poglavar/consensus-builder
Stars
1
Repository age
over a year
Last push
0–30 days ago
Archived
no

Source: the registry entry and api.github.com · 2026-10-24.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 4 record checks met · 4 do not apply · 1 not checked

  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not checkedRepository publishes a security policy (SECURITY.md)We did not read this repository's security policy.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-24. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about xyz.urbangametheory/urban-game-theory

Answered from the data above

Is xyz.urbangametheory/urban-game-theory safe to install?

We do not rate servers as safe or unsafe. 4 of its 4 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does xyz.urbangametheory/urban-game-theory need an API key or sign-in?

It opened a session without any credential on 2026-10-24. The registry entry declares no required credential; no declaration is not a guarantee.

Has xyz.urbangametheory/urban-game-theory been security tested?

Partly. 4 of the 15 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security verdict is published before verification.

Where is the source code of xyz.urbangametheory/urban-game-theory?

In github.com/Poglavar/consensus-builder, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-24
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: exercised
  13. Fake assistant turns: exercised
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

4 exercised11 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 4
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.exercised
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.exercised
Not run, with the reason · 11
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 3
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-10-24, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,564 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 30 tools, 12 resources, 5 prompts.
  4. 15,428 msFinished: 4 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added in the weekly update
listed 2026-10-24; not classified yet
Pricing modelAI-classified
pending: added in the weekly update
the website is not read yet
Programming language
api.github.com · 2026-10-24
Hosting type
registry · 2026-10-24
MCP capability
prompts, resources, tools
our test · 2026-10-24
Transport
streamable HTTP
registry · 2026-10-24
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-24
Lifecycle status
registry · 2026-10-24
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: a personal account · repository age: over a year · stars: 0–9
api.github.com · 2026-10-24
Maintenance
api.github.com · 2026-10-24
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “xyz.urbangametheory/urban-game-theory: MCP server record.” Data checked 2026-10-24. https://protocolprobe.com/mcp/servers/xyz.urbangametheory/urban-game-theory

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 4 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/xyz.urbangametheory/urban-game-theory)](https://protocolprobe.com/mcp/servers/xyz.urbangametheory/urban-game-theory)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology