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.

GVE Public Governed Knowledge

REMOTE · OBJECTS.GLOBALVISIBILITYENGINE.COM

Read-only public, governed enterprise knowledge published by GVE, with provenance and validation.

+3 this week 83 Trust /100

Last scanned (14 hours ago)

Scores higher than 87% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Search and Retrieval

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 Security80
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 492 tokens (~98/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 Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 64% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.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 6 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
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.

  • 5 Nov 26 +1

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

  • 3 Nov 26 +1

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

  • 1 Nov 26 +1

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

  • 29 Oct 26 +1

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

  • 27 Oct 26 +1

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

  • 25 Oct 26 +1

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

  • 23 Oct 26 +1

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

  • 21 Oct 26 +1

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

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 5 Nov 2026 · Probed https://objects.globalvisibilityengine.com/public-enterprise-exposure/_agent/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=objects.globalvisibilityengine.com CN=YE2,O=Let's Encrypt,C=US 12 Sept 2026 11 Dec 2026 ECDSA 256 ECDSA-SHA384 592c773bd1ce86de2312b4a0ceffbe77467
SANs: objects.globalvisibilityengine.com
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

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of objects.globalvisibilityengine.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
globalvisibilityengine.com. 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy same-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://objects.globalvisibilityengine.com/public-enterprise-exposure/_agent/mcp Verified 200
http (plaintext) http://objects.globalvisibilityengine.com/public-enterprise-exposure/_agent/mcp HTTPS enforced 308 https://objects.globalvisibilityengine.com/public-enterprise-exposure/_agent/mcp
MCP tools · 5 exposed · ~292 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
fetch ~31

Fetches the full public object for an id returned by search.

NameTypeReqDescription
idstringyesIdentifier returned by search.
NameTypeReqDescription
idstringyes–
metadataobject––
textstringyes–
titlestringyes–
urlstringyes–

No examples provided.

get_object ~80

Returns one public governed object exactly as GVE serves it publicly, plus its governance view (provenance, validation, quality, last material change; freshness, confidence and relations are reported as not established or not published).

NameTypeReqDescription
idstringyesObject id as listed by list_objects.
namespacestringyes–
typestringyes–
NameTypeReqDescription
governanceobjectyes–
objectobjectyes–

No examples provided.

list_objects ~83

Lists the public objects of one tenant. Without type: the tenant's object types and counts. With type: one page (100 per page) of that type's objects.

NameTypeReqDescription
namespacestringyesTenant namespace from list_tenants.
pageinteger–Page number, from 1.
typestring–Object type from the tenant's types.
NameTypeReqDescription
itemsarray––
linksobject––
namespacestringyes–
pageinteger––
pageCountinteger––
totalObjectsintegeryes–
typestring––
typesarray––

No examples provided.

list_tenants ~30

Lists the organizations whose public governed knowledge GVE publishes, with the object types and counts each one exposes.

Input schema present but exposes no named parameters.

NameTypeReqDescription
tenantsarrayyes–

No examples provided.

search ~68

Lexical search over the labels and descriptions of the public objects. Returns identifiers to pass to fetch.

NameTypeReqDescription
limitinteger––
namespacestring–Optional: restrict to one tenant.
querystringyes–
typestring–Optional: restrict to one object type.
NameTypeReqDescription
resultsarrayyes–

No examples provided.

Install

How do I install the GVE Public Governed Knowledge MCP server?

GVE Public Governed Knowledge is a hosted endpoint at https://objects.globalvisibilityengine.com/public-enterprise-exposure/_agent/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 · objects.globalvisibilityengine.com

# add to Claude Code
claude mcp add --transport http com-globalvisibilityengine-public-knowledge 'https://objects.globalvisibilityengine.com/public-enterprise-exposure/_agent/mcp'
Common questions

What is the GVE Public Governed Knowledge MCP server?

GVE Public Governed Knowledge is an MCP server listed in the public MCP registry as com.globalvisibilityengine/public-knowledge. Read-only public, governed enterprise knowledge published by GVE, with provenance and validation. This page covers its hosted endpoint (https://objects.globalvisibilityengine.com/public-enterprise-exposure/_agent/mcp).

Is the GVE Public Governed Knowledge MCP server safe to use?

GVE Public Governed Knowledge scores 83 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 GVE Public Governed Knowledge MCP server expose?

GVE Public Governed Knowledge exposes 5 tools: list_tenants, list_objects, get_object, search, fetch. Their descriptions and schemas cost roughly 292 tokens of context every time the server is loaded.

Does the GVE Public Governed Knowledge MCP server require authentication?

No. We connected to GVE Public Governed Knowledge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the GVE Public Governed Knowledge MCP server still maintained?

GVE Public Governed Knowledge 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.