Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Ground Truth Worldwide

REMOTE · GT.LLPRO.AI

Cited place facts. Free daily quota; credit keys from $10 at llpro.ai/pay/credit; x402 accepted.

Available components

+10 this week 65 Trust /100

Last scanned (19 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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 Security63
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
  • 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
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 814 tokens (~162/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: schema churn in the 7 days we've observed: 3 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 70% of tool parameters carry a description.Partial
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
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +5
    • Stability: 0.17 → fail ▼ security
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • Tool “feedback.submit” was removed ▼ security
    • Tool “launchpad.start” was removed ▼ security
    • Tool “launchpad.progress” was removed ▼ security
    • Authorization: unverified → partial ▲ security
    • Tool “ground_truth_ask” rewrote its description, which is the text the model reads security
    • Schema quality: 1271 → 814 ▲ functional
    • Tool “feedback_submit” changed its title: Send feedback to LLPRO cosmetic
    • Tool “launchpad_start” changed its title: Start here: get a plan for a goal cosmetic
    • Tool “launchpad_progress” changed its title: Report progress on a plan cosmetic
    • Tool “ground_truth_sources” changed its title: List fact topics and sources cosmetic
    • Tool “ground_truth_ask” changed its title: Ask a public fact cosmetic
  • 19 Nov 26 +3
    • Tool “ground_truth_ask” rewrote its description, which is the text the model reads security
    • MCP protocol: fail → pass ▲ functional
    • MCP protocol version: 2025-03-26 → 2026-07-28 functional
  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1
    • HTTPS: unverified → fail ▼ security
    • Tool “ground_truth_sources” rewrote its description, which is the text the model reads security
    • Schema quality: 136 → 152 ▼ functional
    • “ground_truth_ask” reworded the description of “topic” cosmetic
  • 15 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 14 Nov 26 55

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://gt.llpro.ai/mcp?via=mcp-registry

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=llpro.ai CN=WE1,O=Google Trust Services,C=US 1 Nov 2026 30 Jan 2027 ECDSA 256 ECDSA-SHA256 ffa50cd1836b2a8b0ecd6433c52c4e23
SANs: llpro.ai, *.llpro.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of gt.llpro.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
llpro.ai. No DS 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://gt.llpro.ai/mcp?via=mcp-registry Verified 200
http (plaintext) http://gt.llpro.ai/mcp?via=mcp-registry Served over HTTP 200
MCP tools · 5 exposed · ~814 tokens

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 →

Tool Tokens
feedback_submit ~206

Tell LLPRO what failed, what was missing or what would improve this service. Read daily by the service owner and turned into a fix or an answer; shipped ideas are credited on https://llpro.ai/changelog and earn a contributor mark on Agent Record. Not for support requests that need a reply: write support@llpro.ai for those. Do not send secrets.

NameTypeReqDescription
creditboolean–Default true: credit your agent id on the changelog if the idea ships. Send false to opt out.
messagestring–Anything else, in your own words.
ratinginteger––
toolstring–Which tool or endpoint this is about.
what_failedstring–What did not work, and the call that failed (tool, arguments, what you expected).
what_missingstring–What you needed and could not get.
what_would_improvestring–One concrete change that would make this better.

No output schema declared.

No examples provided.

ground_truth_ask ~290

Use when you need a current, verifiable real-world fact instead of guessing: get cited, time-stamped public facts for anywhere on Earth: weather, river levels, floods, earthquakes, disasters, air quality, US weather alerts (road closures, power outages, burn bans report 'not connected' until sources exist). Every answer has fact, place, time, source_url, age_seconds, stale, confidence. Free daily quota; credit keys from $1 at llpro.ai/pay/credit; x402 accepted. Send the key as Authorization: Bearer <llk_ key>. We charge only while this tool passes today's known-answer test; in testing it answers free.

NameTypeReqDescription
latnumber––
lonnumber––
max_age_minutesnumber–Mark answers older than this as stale
placestring–Any place name, e.g. 'Lafayette' or 'Lagos, Nigeria'; or use lat+lon
topicstringyesOne of: weather, weather_alerts, river_level, flood, earthquakes, disasters, air_quality, road_closures, power_outages, burn_ban (or give free text in q and the topic is guessed). Not connected yet:…

No output schema declared.

No examples provided.

ground_truth_sources ~67

List every Ground Truth topic, the public source behind it and whether that source is connected yet. Use it when you want to know what ground_truth_ask can answer before you ask, or which agency a fact comes from. Takes no input. Free, read-only, no sign-up.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

launchpad_progress ~104

Report where you are on a Launchpad plan and get the next step, an on-track check and, if you are stuck, a way round. Needs the launch_id and token from launchpad.start.

NameTypeReqDescription
launch_idstringyes–
reasonstring–Only with status stuck.
statusstring––
stepstring–A step id from your plan. Leave out to ask where you are.
tokenstringyes–

No output schema declared.

No examples provided.

launchpad_start ~147

Stuck? Start here. Give your goal and any limits; get back a concrete plan (LLPRO tools first, then registries and the open web), the first task to run, and a token to report progress. Free. The goal is read for keywords only and is never stored. Anything that spends, signs, sends, shares, connects or deletes is marked as needing your owner's approval.

NameTypeReqDescription
agent_idstring–A stable name for you. Used only to count return visits.
constraintsobject–Optional limits. They only ever make the plan stricter.
goalstringyesWhat you are trying to get done, in a sentence or two.

No output schema declared.

No examples provided.

Install

How do I install the Ground Truth Worldwide MCP server?

Ground Truth Worldwide is a hosted endpoint at https://gt.llpro.ai/mcp?via=mcp-registry, 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 · gt.llpro.ai

# add to Claude Code
claude mcp add --transport http ai-llpro-gt-ground-truth-worldwide 'https://gt.llpro.ai/mcp?via=mcp-registry'
Common questions

What is the Ground Truth Worldwide MCP server?

Ground Truth Worldwide is an MCP server listed in the public MCP registry as ai.llpro.gt/ground-truth-worldwide. Cited place facts. Free daily quota; credit keys from $10 at llpro.ai/pay/credit; x402 accepted. This page covers its hosted endpoint (https://gt.llpro.ai/mcp?via=mcp-registry).

Is the Ground Truth Worldwide MCP server safe to use?

Ground Truth Worldwide scores 65 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 Ground Truth Worldwide MCP server expose?

Ground Truth Worldwide exposes 5 tools: ground_truth_ask, ground_truth_sources, feedback_submit, launchpad_start, launchpad_progress. Their descriptions and schemas cost roughly 814 tokens of context every time the server is loaded.

Does the Ground Truth Worldwide MCP server require authentication?

No. We connected to Ground Truth Worldwide without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Ground Truth Worldwide MCP server still maintained?

Ground Truth Worldwide is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Ground Truth Worldwide MCP server?

VerifyMCP ran 13 checks on Ground Truth Worldwide, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.