Edgepedia

Is Edgepedia MCP server safe?

• None of the hidden-instruction wordings we know were found in its tool descriptions.
• Its error messages showed no secrets or internal details.
• All 5 of its tools are labeled read-only.
• Overall it scored 98/100 on 1 Nov 2026.

A test can only see what the server shows from outside, not what it does with your data behind the scenes. Connect servers from makers you trust.

What it can do

5 tools, in the server's own words.

Test results

Safe mode: only tools labeled read-only were run. How the test works

• !
  Fast enough

  1 warning

  • !fetch: Slowest tool: fetch (3.1 s): users will notice the wait
  • and 3 more
  note
• !
  Follows MCP best practices (not scored yet)

  1 tip (not scored)

  • !Very common tool names: search, fetch. Next to other servers' tools the AI may mix them up; a short prefix helps (like "github_search" instead of "search").
  note
• ✓
  ConnectsConnected in 295 ms
  pass
• ✓
  Ready for the newest MCP versionUses the latest MCP version (2026-07-28)
  pass
• ✓
  Lists its toolsFound 5 tools
  pass
• ✓
  Every tool is describedAll 5 tools and their inputs are described
  pass
• ✓
  Tools are labeled safe or dangerousEvery tool has a safety label
  pass
• ✓
  No known hidden instructionsNone of the hidden-instruction wordings we know were found in tool descriptions. New wordings can get past this check.
  pass
• ✓
  Tools work with good inputs

  All good

  • ✓search: Worked (1.2 s)
  • ✓fetch: Worked (3.1 s)
  • ✓related: Answered with an error, probably because of our sample input: No article has that id. Use `search` first, then pass a result's id. Did you mean Test cricket (id: test-cricket), Ames test (id: ames-test…
  • ✓connect: Answered with an error, probably because of our sample input: No such article: from "test". Use `search` first, then pass a result's id.
  • ✓resolve: Worked (2.6 s)
  pass
• ✓
  Bad inputs give a clean error

  All good

  • ✓search: Refused missing required input "query" with a clear error
  • ✓search: Refused wrong type for "query" with a clear error
  • ✓fetch: Refused missing required input "id" with a clear error
  • ✓fetch: Refused wrong type for "id" with a clear error
  • ✓related: Refused missing required input "id" with a clear error
  • ✓related: Refused wrong type for "id" with a clear error
  • ✓connect: Refused missing required input "from" with a clear error
  • ✓connect: Refused wrong type for "from" with a clear error
  • and 2 more
  pass
• ✓
  Tools work together

  5 chains working

  • ✓search → fetch: fetch found what search returned (id = "test-cricket")
  • ✓search → related: related found what search returned (id = "test-cricket")
  • ✓fetch → related: related found what fetch returned (id = "test-cricket")
  • ✓resolve → fetch: fetch found what resolve returned (id = "test-2025-film")
  • ✓resolve → related: related found what resolve returned (id = "test-2025-film")
  pass
• ✓
  No secrets leakedChecked 17 error messages: no secrets or internal details
  pass
• ✓
  Resources and prompts work

  All good (2 templates)

  • ✓edgepedia://article/{slug}: A made-up value gets a clean error (edgepedia://article/qamcp-test)
  • ✓edgepedia://topic/{id}: A made-up value gets a clean error (edgepedia://topic/qamcp-test)
  • ✓An address that does not exist gets a clean "not found" error
  pass

Test it yourself

Free and open source. Same checks, same score.

Show this score on GitHub

Free for every server in the directory. Paste this into your README: the badge shows the score from our latest test.

Score over time

• 1 Nov 202698

One test so far. New tests will show here.

Reviews

Coming soon: reviews from people who use Edgepedia, signed in with GitHub, one per person. Reviews never change the score.