# GVE Public Governed Knowledge (remote · objects.globalvisibilityengine.com)

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

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `objects.globalvisibilityengine.com`: 83/100 (this document), [markdown](https://verifymcp.io/servers/com-globalvisibilityengine-public-knowledge/public-enterprise-exposure-agent-mcp.md), [page](https://verifymcp.io/servers/com-globalvisibilityengine-public-knowledge/public-enterprise-exposure-agent-mcp)

## Channel facts

- Endpoint: `https://objects.globalvisibilityengine.com/public-enterprise-exposure/_agent/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 492 tokens (~98/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 64% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## 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.

### Claude

```bash
claude mcp add --transport http com-globalvisibilityengine-public-knowledge 'https://objects.globalvisibilityengine.com/public-enterprise-exposure/_agent/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-globalvisibilityengine-public-knowledge": {
      "url": "https://objects.globalvisibilityengine.com/public-enterprise-exposure/_agent/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-globalvisibilityengine-public-knowledge": {
      "type": "http",
      "url": "https://objects.globalvisibilityengine.com/public-enterprise-exposure/_agent/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-globalvisibilityengine-public-knowledge]
url = "https://objects.globalvisibilityengine.com/public-enterprise-exposure/_agent/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-globalvisibilityengine-public-knowledge": {
      "type": "remote",
      "url": "https://objects.globalvisibilityengine.com/public-enterprise-exposure/_agent/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-globalvisibilityengine-public-knowledge --url 'https://objects.globalvisibilityengine.com/public-enterprise-exposure/_agent/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-globalvisibilityengine-public-knowledge:
    url: "https://objects.globalvisibilityengine.com/public-enterprise-exposure/_agent/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-globalvisibilityengine-public-knowledge": {
      "Transport": "http",
      "Url": "https://objects.globalvisibilityengine.com/public-enterprise-exposure/_agent/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-globalvisibilityengine-public-knowledge -t streamable-http -u 'https://objects.globalvisibilityengine.com/public-enterprise-exposure/_agent/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-globalvisibilityengine-public-knowledge": {
      "type": "http",
      "url": "https://objects.globalvisibilityengine.com/public-enterprise-exposure/_agent/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 83, +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.

### 2026-11-03 (score 82, +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.

### 2026-11-01 (score 81, +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.

### 2026-10-29 (score 80, +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.

### 2026-10-27 (score 79, +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.

### 2026-10-25 (score 78, +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.

### 2026-10-23 (score 77, +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.

### 2026-10-21 (score 76, +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.

## MCP tools (5)

### `list_tenants` (~30 tokens)

List public knowledge tenants

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

Output parameters:

- `tenants` (array)

### `list_objects` (~83 tokens)

List public objects

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.

Input parameters:

- `namespace` (string, required): Tenant namespace from list_tenants.
- `page` (integer): Page number, from 1.
- `type` (string): Object type from the tenant's types.

Output parameters:

- `items` (array)
- `links` (object)
- `namespace` (string)
- `page` (integer)
- `pageCount` (integer)
- `totalObjects` (integer)
- `type` (string)
- `types` (array)

### `get_object` (~80 tokens)

Get one public object

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).

Input parameters:

- `id` (string, required): Object id as listed by list_objects.
- `namespace` (string, required)
- `type` (string, required)

Output parameters:

- `governance` (object)
- `object` (object)

### `search` (~68 tokens)

Search public objects

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

Input parameters:

- `limit` (integer)
- `namespace` (string): Optional: restrict to one tenant.
- `query` (string, required)
- `type` (string): Optional: restrict to one object type.

Output parameters:

- `results` (array)

### `fetch` (~31 tokens)

Fetch a search result

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

Input parameters:

- `id` (string, required): Identifier returned by search.

Output parameters:

- `id` (string)
- `metadata` (object)
- `text` (string)
- `title` (string)
- `url` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-globalvisibilityengine-public-knowledge/public-enterprise-exposure-agent-mcp#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 80
- 2026-10-28: 79
- 2026-10-27: 79
- 2026-10-26: 78
- 2026-10-25: 78
- 2026-10-24: 77
- 2026-10-23: 77
- 2026-10-22: 76
- 2026-10-21: 76
- 2026-10-20: 75
- 2026-10-19: 75
- 2026-10-18: 74
- 2026-10-17: 74
- 2026-10-16: 73
- 2026-10-15: 73
- 2026-10-14: 73
- 2026-10-13: 72
- 2026-10-12: 72

## 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.

### What did VerifyMCP test on the GVE Public Governed Knowledge MCP server?

VerifyMCP ran 13 checks on GVE Public Governed Knowledge, 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.

## Links

- Remote endpoint: https://objects.globalvisibilityengine.com/public-enterprise-exposure/_agent/mcp
- Website: https://globalvisibilityengine.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-globalvisibilityengine-public-knowledge/public-enterprise-exposure-agent-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-globalvisibilityengine-public-knowledge/public-enterprise-exposure-agent-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-globalvisibilityengine-public-knowledge/public-enterprise-exposure-agent-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-globalvisibilityengine-public-knowledge/public-enterprise-exposure-agent-mcp