DataGraph
REMOTE · API.DATAGRAPH.CITY · 2 COMPONENTS · SCANNED AUG 3
Urban intelligence knowledge graph. Structured locality data for civic problem-solving.
Available components
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 →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.datagraph.city
claude mcp add --transport http team-earth-datagraph https://api.datagraph.city/mcp
[mcp_servers.team-earth-datagraph] url = "https://api.datagraph.city/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"team-earth-datagraph": {
"type": "remote",
"url": "https://api.datagraph.city/mcp",
"enabled": true
}
}
} openclaw mcp add team-earth-datagraph --url https://api.datagraph.city/mcp --transport streamable-http
mcp_servers:
team-earth-datagraph:
url: "https://api.datagraph.city/mcp" {
"mcpServers": {
"team-earth-datagraph": {
"type": "http",
"url": "https://api.datagraph.city/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 61
First indexed and scored.
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 3 Aug 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=YE2,O=Let's Encrypt,C=US | 16 Jun 2026 | 14 Sept 2026 | ECDSA 256 | ECDSA-SHA384 | 5b8b4aa65624a076cb7f002f80b42728865 |
| SANs: api.datagraph.city | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 |
DNSSEC insecure
Validation of api.datagraph.city. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| city. | present | 32800 | 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 |
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.
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.