DataGraph
REMOTE · API.DATAGRAPH.CITY · 2 COMPONENTS
Urban intelligence knowledge graph. Structured locality data for civic problem-solving.
Available components
Last scanned (2 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 294 tokens (~58/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.datagraph.city/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.datagraph.city | CN=YE1,O=Let's Encrypt,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 67fa9e197a3bb1d4b9406e9a8d10c234b1b |
| SANs: api.datagraph.city | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.datagraph.city. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| city. | present | 57326 | 8 | Verified |
| datagraph.city. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.datagraph.city/mcp | Verified | 200 | |
| http (plaintext) | http://api.datagraph.city/mcp | HTTPS enforced | 301 | https://api.datagraph.city/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_locality_schema ~79
Get the graph schema for a locality (node types, relationships, sample queries). Call list_datasets first to get locality codes.
| Name | Type | Req | Description |
|---|---|---|---|
| locality | string | yes | Locality code (REQUIRED). Use the 'locality' field from list_datasets. Example: 'nova-scotia', 'kc', 'unlonely-nyc'. |
No output schema declared.
No examples provided.
get_server_info ~22
Get DataGraph MCP server metadata and GOSR framework info.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_usage_stats ~19
Check your API usage and quota. Requires auth.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_datasets ~33
List available datasets. Optionally filter by locality code.
| Name | Type | Req | Description |
|---|---|---|---|
| locality | string | – | Filter by locality code (optional) |
No output schema declared.
No examples provided.
query_locality_data ~141
Query data using natural language or Cypher. Requires auth.
| Name | Type | Req | Description |
|---|---|---|---|
| cypher_params | object | – | Parameters for Cypher query ($param syntax). |
| cypher_query | string | – | RECOMMENDED: Cypher query generated from schema. MUST include WHERE n.dataset = '<dataset_id>' filter. Must be read-only with LIMIT clause (max 1000). |
| limit | number | – | Max results for NL queries (default: 10, max: 100) |
| locality | string | – | Locality code (REQUIRED). Use the 'locality' field from list_datasets. |
| query | string | yes | User question or description. |
No output schema declared.
No examples provided.
How do I install the DataGraph MCP server?
DataGraph is a hosted endpoint at https://api.datagraph.city/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.datagraph.city
claude mcp add --transport http team-earth-datagraph 'https://api.datagraph.city/mcp'
What is the DataGraph MCP server?
DataGraph is an MCP server listed in the public MCP registry as io.github.team-earth/datagraph. Urban intelligence knowledge graph. Structured locality data for civic problem-solving. This page covers its hosted endpoint (https://api.datagraph.city/mcp).
Is the DataGraph MCP server safe to use?
DataGraph scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the DataGraph MCP server expose?
DataGraph exposes 5 tools: get_server_info, list_datasets, get_locality_schema, query_locality_data, get_usage_stats. Their descriptions and schemas cost roughly 294 tokens of context every time the server is loaded.
Does the DataGraph MCP server require authentication?
No. We connected to DataGraph without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the DataGraph MCP server still maintained?
DataGraph is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.