Skip to content

PHION Evidence Engine

Fetches a public web source for AI agents, screens it for prompt injection, and returns an Ed25519-signed receipt of the observed content.
At a glanceswept Oct 26, 2026

not read yet

Use

For
AI agents and developers who need signed, verifiable evidence from public web sources
Runs as
API
Used for
  • fetch a public web source and screen it for prompt injection
  • hash normalized observations and issue ed25519 signed receipts
  • verify evidence receipts offline without network access
Worth knowingcomputed from what we read · each with its source
How a program reaches itfound, not claimed · read Oct 26, 2026
  • MCP serversystems.phion/evidence-engineverified in the MCP registry
  • Stateanswers, 1 toolschecked 2026-10-26
  • Address to connectphion.systems/mcp/task
  • OpenAPI spec175 pathsthe spec ↗

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Agentsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare PHION Evidence Engine with

Pick up to two.

All 10 alternatives to PHION Evidence Engine →

All Agents tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use PHION Evidence Engine for?

Sign in to leave a note
Questions this page answers
  • What is PHION Evidence Engine?

    Fetches a public web source for AI agents, screens it for prompt injection, and returns an Ed25519-signed receipt of the observed content. It is listed in the Atlas under Agents.

  • Who is PHION Evidence Engine for?

    AI agents and developers who need signed, verifiable evidence from public web sources

  • Do people use PHION Evidence Engine?

    Little sign of use.

  • What are alternatives to PHION Evidence Engine?

    In Agents, by use: Genspark, Pickaxe, Browserless, You.com, Speakeasy, Twin.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk