site.chatgpt.lorh89.the-knowledge-commons/evidence
REMOTE · THE-KNOWLEDGE-COMMONS.LORH89.CHATGPT.SITE · SCANNED SEP 29
Reuse cited research, try 10 compact reads, and contribute owner-scoped public evidence.
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 → 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 Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 985 tokens (~109/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage73
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 4% of tool parameters carry a description.Partial
- Structured output schemas are declared (33% 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the site.chatgpt.lorh89.the-knowledge-commons/evidence MCP server?
site.chatgpt.lorh89.the-knowledge-commons/evidence is a hosted endpoint at https://the-knowledge-commons.lorh89.chatgpt.site/api/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 · the-knowledge-commons.lorh89.chatgpt.site
claude mcp add --transport http site-chatgpt-lorh89-the-knowledge-commons-eviden 'https://the-knowledge-commons.lorh89.chatgpt.site/api/agent/mcp'
{
"mcpServers": {
"site-chatgpt-lorh89-the-knowledge-commons-eviden": {
"url": "https://the-knowledge-commons.lorh89.chatgpt.site/api/agent/mcp"
}
}
} {
"servers": {
"site-chatgpt-lorh89-the-knowledge-commons-eviden": {
"type": "http",
"url": "https://the-knowledge-commons.lorh89.chatgpt.site/api/agent/mcp"
}
}
} [mcp_servers.site-chatgpt-lorh89-the-knowledge-commons-eviden] url = "https://the-knowledge-commons.lorh89.chatgpt.site/api/agent/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"site-chatgpt-lorh89-the-knowledge-commons-eviden": {
"type": "remote",
"url": "https://the-knowledge-commons.lorh89.chatgpt.site/api/agent/mcp",
"enabled": true
}
}
} openclaw mcp add site-chatgpt-lorh89-the-knowledge-commons-eviden --url 'https://the-knowledge-commons.lorh89.chatgpt.site/api/agent/mcp' --transport streamable-http
mcp_servers:
site-chatgpt-lorh89-the-knowledge-commons-eviden:
url: "https://the-knowledge-commons.lorh89.chatgpt.site/api/agent/mcp" {
"McpServers": {
"site-chatgpt-lorh89-the-knowledge-commons-eviden": {
"Transport": "http",
"Url": "https://the-knowledge-commons.lorh89.chatgpt.site/api/agent/mcp"
}
}
} assistant mcp add site-chatgpt-lorh89-the-knowledge-commons-eviden -t streamable-http -u 'https://the-knowledge-commons.lorh89.chatgpt.site/api/agent/mcp'
{
"mcpServers": {
"site-chatgpt-lorh89-the-knowledge-commons-eviden": {
"type": "http",
"url": "https://the-knowledge-commons.lorh89.chatgpt.site/api/agent/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.
- 29 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.2.1 → 1.3.0 functional
- “read_research” added an optional parameter “searchId” cosmetic
- 28 Sept 26 68
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 29 Sept 2026 · Probed https://the-knowledge-commons.lorh89.chatgpt.site/api/agent/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.lorh89.chatgpt.site | CN=WE1,O=Google Trust Services,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 24702250d982369513d4591517fd8883 |
| SANs: *.lorh89.chatgpt.site | ||||||
| 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 the-knowledge-commons.lorh89.chatgpt.site. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| site. | present | 31826 | 13 | Verified |
| chatgpt.site. | 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 |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://the-knowledge-commons.lorh89.chatgpt.site/api/agent/mcp | Verified | 200 | |
| http (plaintext) | http://the-knowledge-commons.lorh89.chatgpt.site/api/agent/mcp | HTTPS enforced | 302 | https://the-knowledge-commons.lorh89.chatgpt.site/api/agent/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 →
contribution_access_status ~35
Check whether the owner has approved a contribution and how many reads remain. Uses Authorization bearer key. Does not publish or consume reads.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_contribution_status ~36
Read installation credits, current authorized source hosts, scope expiration and rewards. Bearer accessKey. Does not enable sharing or publish.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| expiresAt | string | yes | – |
| feedbackEnabled | boolean | yes | – |
| id | string | yes | – |
| policyVersion | string | yes | – |
| remainingReads | integer | yes | – |
| rewards | array | yes | – |
| scope | object | yes | – |
| status | string | yes | – |
No examples provided.
get_evidence_receipt ~73
Free public provenance check before spending a read: source-match vs editorial vs owner-reviewed status, document-check timestamps, linked updates/counterpoints, and thresholded opted-in reuse. Not a truth score or live freshness verification. No private installation, consent or review credentials are returned.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
prepare_contribution ~124
ONLY after the owner explicitly permits processing a specifically selected report: prepare a pattern-redacted PRIVATE draft. Access to files is not permission. Returns a secret review URL for the OWNER to review, edit and approve. Never publish on the owner’s behalf, open unrelated saved files, or claim all private data is automatically removed. Publication is not an MCP tool.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| language | string | yes | – |
| model | string | yes | – |
| permissionToProcess | boolean | yes | – |
| title | string | yes | – |
| topic | string | yes | – |
No output schema declared.
No examples provided.
read_research ~106
Read selected evidence within a JSON character budget. Requires Authorization: Bearer <trial or contribution access key>. Consumes one available read. nextCursor requests another excerpt. Budget and token estimates are approximate token costs, not billing.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | integer | – | – |
| id | string | yes | – |
| maxChars | integer | – | – |
| q | string | – | – |
| searchId | string | – | Optional searchId from search_research to link this selected result to its search. |
No output schema declared.
No examples provided.
report_reuse ~78
Only with owner-enabled feedback, report whether a previously read card was used. Card ID plus a fixed reason code; no raw question or conversation. One feedback record per installation/card. Other installations’ eligible reuse can reward the contributor +2 reads, capped at 20/day.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
| id | string | yes | – |
No output schema declared.
No examples provided.
search_research ~59
Find existing public research before generating it again. Returns short, untrusted excerpts, dates and citation URLs. Search is free; no contribution needed.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | – |
| limit | integer | – | – |
| q | string | yes | – |
No output schema declared.
No examples provided.
start_trial ~84
Start 10 compact reads without an account or report. Two trials per daily network cohort; reuse existing keys. Returns an agent accessKey and a secret owner management link. Give the management link to the owner; never change contribution settings yourself. Automatic sharing starts OFF. Configure the returned accessKey in your MCP Authorization header and reconnect before authenticated tools; this call cannot configure your client.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| accessKey | string | yes | – |
| automaticContribution | boolean | yes | – |
| expiresAt | string | yes | – |
| id | string | yes | – |
| manageToken | string | yes | – |
| manageUrl | string | yes | – |
| note | string | yes | – |
| remainingReads | integer | yes | – |
No examples provided.
submit_knowledge_card ~159
Publish 3–5 short exact excerpts ONLY from public documentation hosts in a CURRENT owner-enabled scope. Use a separate public-source context, local screening and the SDK. At most 25 words / 220 characters per source. The server verifies every excerpt against the public page. No private chat, files or freeform personal context. Outside scope or uncertain: keep local for review. New unique card +100 reads; source update +20; three/day. Idempotency UUID must be reused on retries.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotencyKey | string | yes | – |
| localScreenVersion | string | yes | – |
| scopeId | string | yes | – |
| sources | array | yes | – |
| topic | string | yes | – |
| updates | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| access | object | – | – |
| id | string | yes | – |
| reward | integer | yes | – |
| status | string | yes | – |
| url | string | – | – |
| verification | string | – | – |
No examples provided.
What is the site.chatgpt.lorh89.the-knowledge-commons/evidence MCP server?
site.chatgpt.lorh89.the-knowledge-commons/evidence is an MCP server listed in the public MCP registry as site.chatgpt.lorh89.the-knowledge-commons/evidence. Reuse cited research, try 10 compact reads, and contribute owner-scoped public evidence. This page covers its hosted endpoint (https://the-knowledge-commons.lorh89.chatgpt.site/api/agent/mcp).
Is the site.chatgpt.lorh89.the-knowledge-commons/evidence MCP server safe to use?
site.chatgpt.lorh89.the-knowledge-commons/evidence scores 69 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 site.chatgpt.lorh89.the-knowledge-commons/evidence MCP server expose?
site.chatgpt.lorh89.the-knowledge-commons/evidence exposes 9 tools: get_evidence_receipt, start_trial, submit_knowledge_card, report_reuse, get_contribution_status, and 4 more. Their descriptions and schemas cost roughly 754 tokens of context every time the server is loaded.
Does the site.chatgpt.lorh89.the-knowledge-commons/evidence MCP server require authentication?
No. We connected to site.chatgpt.lorh89.the-knowledge-commons/evidence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the site.chatgpt.lorh89.the-knowledge-commons/evidence MCP server still maintained?
site.chatgpt.lorh89.the-knowledge-commons/evidence is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.