Edgepedia
REMOTE · WWW.EDGECHAT.AI
Search and read Edgepedia, a free and growing encyclopedia with citations. No key.
Available components
Last scanned (10 hours ago)
Scores higher than 10% of remote servers
Reachable. Last reached 22 Nov 2026.
Category Education and Research
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
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (5)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
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 →
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.
- 13 Nov 26 −60
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 12 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 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
- 3 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
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 22 Nov 2026 · Probed https://www.edgechat.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.edgechat.ai | CN=YR1,O=Let's Encrypt,C=US | 21 Oct 2026 | 19 Jan 2027 | RSA 2048 | SHA256-RSA | 6ef5617dfad9198b6a6e52bb5f3e8428391 |
| SANs: www.edgechat.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.edgechat.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| edgechat.ai. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 308 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | object-src 'none'; base-uri 'self'; frame-ancestors 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.edgechat.ai/mcp | Redirected | 308 | https://www.edgepedia.org/mcp |
| http (plaintext) | http://www.edgechat.ai/mcp | HTTPS enforced | 308 | https://www.edgechat.ai/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 →
connect Connect two Edgepedia articles ~89
Find the shortest chain of in-text links from one Edgepedia article to another (at most 6 hops), with the sentence that makes each hop; pass two ids as `search` returns them.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | The starting article's id (such as "koala"), its ep… id, or its title. |
| to | string | yes | The target article, named the same ways. |
| Name | Type | Req | Description |
|---|---|---|---|
| found | boolean | yes | – |
| from | string | yes | – |
| hops | integer | – | – |
| path | array | – | – |
| reason | string | – | – |
| steps | array | – | – |
| text | string | yes | – |
| to | string | yes | – |
No examples provided.
fetch Fetch an Edgepedia article ~545
Read an encyclopedia article in full: one Edgepedia article as Markdown with its citations, by a `search` result's id. Returns id, title, text, url, and metadata (topic path, license, credit). A `topic:` id lists that topic's parent, narrower topics, and articles, 120 a page; `topic:root` is the top of the tree, `topic:geo` the geography tree. `citations: false` gives [n] markers instead of inline source links. Show the `credit` line with any text you quote.
| Name | Type | Req | Description |
|---|---|---|---|
| chunks | boolean | – | true = the text as paragraphs with stable ids, in `chunks`. |
| citations | boolean | – | Default true. false = [n] markers instead of inline source links; the numbered reference list stays. |
| cite | string | – | Add a reference in this format (csl, bibtex, ris, apa, mla, chicago, harvard). |
| cursor | string | – | Where to continue, from a cut text's `next_cursor`. |
| format | string | – | The text as plain text, HTML, JSON-LD, or Turtle instead of Markdown. |
| id | string | yes | The id of a search result (the last part of the article's address, such as "mount-fuji", or a topic's "topic:…" id). |
| ids | array | – | More ids to fetch with `id` in one call, up to 10 in all. |
| length | string | – | snippet or lead for a short text; full (default) for the whole article. |
| links | string | – | Add the articles linking here (in), the links it makes (out), or both. |
| links_page | integer | – | With links "in" or "both": which 30 articles linking here, from 1. |
| max_tokens | integer | – | Cut the text at a section boundary to about this many tokens; pass `next_cursor` as `cursor` for the rest. |
| outline | boolean | – | true = add the list of the article's headings. |
| page | integer | – | A topic only: which page of its articles, from 1. |
| query | string | – | Only the 3 passages that best match these words, each with a `cite_url`. |
| quote | string | – | A sentence from the article, or a chunk id: adds a `cite_url` that opens the page at it. |
| section | string | – | Only this section, by its heading ("Etymology", "History"). |
| tables | boolean | – | true = add the article's tables as JSON and CSV. |
| Name | Type | Req | Description |
|---|---|---|---|
| canonical_id | string | – | The article's permanent id (ep…); `fetch` takes it, and it outlives an address change. |
| id | string | – | – |
| metadata | object | – | – |
| moved_from | string | – | The id asked for, when the article has since moved; store `id` or `canonical_id` instead. |
| results | array | – | With `ids`: one entry per id, in order: that fetch's answer, or { id, error: { code, message } }. |
| text | string | – | – |
| title | string | – | – |
| url | string | – | – |
No examples provided.
related Related Edgepedia articles ~110
Find encyclopedia articles related to an Edgepedia article: its topic-mates, a few from each neighboring topic, and its geography neighbors. Pass its id, as for `fetch`. Returns groups of results; `fetch` a group's `topic` id for more.
| Name | Type | Req | Description |
|---|---|---|---|
| by | string | – | "links" = articles cited together with it, and articles linking to what it links to. |
| id | string | yes | An article's id, as `search` returns it (such as "mount-fuji"). |
| Name | Type | Req | Description |
|---|---|---|---|
| by | string | – | – |
| cocited | array | – | – |
| coupled | array | – | – |
| cousins | array | – | – |
| geo | array | – | – |
| id | string | – | – |
| siblings | object|null | – | – |
| title | string | – | – |
| url | string | – | – |
No examples provided.
resolve Resolve a name to an Edgepedia article ~189
Find which encyclopedia article a name means: Edgepedia's best match for a person, place, thing, or concept named in a text, with a confidence, whether the name is ambiguous, and the alternatives. Pass the name ("Mercury"), and optionally words from the text around it (`context`: "planet orbit") or a topic id the article must sit under (`type`). Returns `result` (id, title, url) and `alternatives`; pass an id to `fetch`.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Words from the text around the name, which favor the article they fit. |
| limit | integer | – | Candidates to return, 1 to 10 (default 5). |
| name | string | yes | The name as the text gives it. |
| type | string | – | Only articles under this topic id (as `fetch` topic:… names it, without "topic:"). |
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | array | yes | – |
| ambiguous | boolean | yes | – |
| confidence | number | yes | – |
| match | string | yes | – |
| query | string | yes | – |
| result | – | yes | – |
No examples provided.
search Search Edgepedia ~238
Search an encyclopedia for facts about a person, place, thing, event, or concept: Edgepedia, more than 500,000 articles with citations. Pass the subject's name ("Mount Fuji", "photosynthesis"), not a question; other names and misspellings match, and when no title matches, articles whose text does follow, marked `match: fulltext`. Returns results with id, title, url, and preview text, plus a `topic:` result when the query names a topic ("painters"); pass an id to `fetch`. `limit` and `page` reach further results.
| Name | Type | Req | Description |
|---|---|---|---|
| first | boolean | – | true = only the best match. |
| limit | integer | – | Results a page, 1 to 30 (default 10). |
| page | integer | – | Which page of results, from 1. |
| query | string | yes | The name of a subject, or words from an article title. |
| sort | string | – | central = the most-linked subjects first. |
| topic | string | – | Only articles under this topic id (as `fetch` topic:… names it, without "topic:"). |
| Name | Type | Req | Description |
|---|---|---|---|
| did_you_mean | string | – | – |
| page | integer | – | – |
| pages | integer | – | Pages of results at this limit; pass `page` for the next. |
| results | array | yes | – |
No examples provided.
How do I install the Edgepedia MCP server?
Edgepedia is a hosted endpoint at https://www.edgechat.ai/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 · www.edgechat.ai
claude mcp add --transport http ai-edgechat-edgepedia 'https://www.edgechat.ai/mcp'
What is the Edgepedia MCP server?
Edgepedia is an MCP server listed in the public MCP registry as ai.edgechat/edgepedia. Search and read Edgepedia, a free and growing encyclopedia with citations. No key. This page covers its hosted endpoint (https://www.edgechat.ai/mcp).
Is the Edgepedia MCP server safe to use?
Edgepedia scores 25 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 Edgepedia MCP server expose?
Edgepedia exposes 5 tools: search, fetch, related, connect, resolve. Their descriptions and schemas cost roughly 1,171 tokens of context every time the server is loaded.
Does the Edgepedia MCP server require authentication?
Its publisher declares no required credentials for Edgepedia. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Edgepedia MCP server still maintained?
Edgepedia is still listed as active in the MCP registry. We last reached this channel on 22 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 Edgepedia MCP server?
VerifyMCP ran 5 checks on Edgepedia, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Edgepedia: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.