Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PHION Task Router

REMOTE · PHION.SYSTEMS

Find, authorize and verify the best eligible service for an agent task in one compact MCP journey.

Available components

69 Trust /100

Last scanned (21 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 21 Nov 2026.

Trust breakdown (7 categories)

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 Security80
  • 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. 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. See how to fix → View diagnostics → Partial
  • 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 & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 351 tokens (~87/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 13% of tool parameters carry a description.Partial
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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

Changelog

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 18 Nov 26 68

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://phion.systems/mcp/task?phion_source=mcp_registry

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=phion.systems CN=YE1,O=Let's Encrypt,C=US 27 Sept 2026 26 Dec 2026 ECDSA 256 ECDSA-SHA384 5730efa004f804f7be04be2da121beb3e36
SANs: phion.systems, www.phion.systems
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of phion.systems. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
systems. DS published 13097 8 Verified
phion.systems. No DS 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
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy default-src 'self' https://*.cloudflare.com https://gstatic.com; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://*.jsdelivr.net https://*.cloudflare.com https://*.unpkg.com; style-src 'self' 'unsafe-inline' https://googleapis.com; connect-src 'self' https://*.walletconnect.com https://*.cloudflare-eth.com; img-src 'self' data: https://*.phion.systems https://*.reown.com; font-src 'self' https://gstatic.com;
x-content-type-options nosniff
x-frame-options DENY
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://phion.systems/mcp/task?phion_source=mcp_registry Verified 200
http (plaintext) http://phion.systems/mcp/task?phion_source=mcp_registry HTTPS enforced 301 https://phion.systems/mcp/task?phion_source=mcp_registry
MCP tools · 4 exposed · ~351 tokens

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 →

Tool Tokens
authorize_and_execute_selected_task ~138

After find_or_quote_task selects a service, submit its input, an idempotency key and an explicit maximum atomic-USDC budget. The first call returns payment requirements without execution; an x402-aware client may obtain local approval and retry this identical MCP call with payment metadata. PHION never receives a private key and never expands the stated budget.

NameTypeReqDescription
acceptance_criteriaarray––
dry_runboolean––
idempotency_keystringyes–
inputobjectyes–
max_budget_atomicstringyes–
objectivestringyes–
target_servicestringyes–

No output schema declared.

No examples provided.

find_best_service_for_task ~61

Compatibility alias for find_or_quote_task. Free, advisory and non-executing.

NameTypeReqDescription
constraintsobject––
taskstringyesThe outcome the agent needs, written naturally; do not translate it into a PHION service name.

No output schema declared.

No examples provided.

find_or_quote_task ~75

Start here. Describe the desired result in ordinary language. PHION identifies the exact service, input schema, price ceiling and next call without charging or executing anything.

NameTypeReqDescription
constraintsobject––
taskstringyesThe outcome the agent needs, written naturally; do not translate it into a PHION service name.

No output schema declared.

No examples provided.

verify_or_explain_result ~77

Verify a PHION receipt for free, or turn a structured failed status into one safe next action. This tool never charges, retries, or executes a provider.

NameTypeReqDescription
content–––
failureobject––
receiptobject––
sourcesarray––
statusCodeinteger––

No output schema declared.

No examples provided.

Install

How do I install the PHION Task Router MCP server?

PHION Task Router is a hosted endpoint at https://phion.systems/mcp/task?phion_source=mcp_registry, 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 · phion.systems

# add to Claude Code
claude mcp add --transport http systems-phion-evidence-engine 'https://phion.systems/mcp/task?phion_source=mcp_registry'
Common questions

What is the PHION Task Router MCP server?

PHION Task Router is an MCP server listed in the public MCP registry as systems.phion/evidence-engine. Find, authorize and verify the best eligible service for an agent task in one compact MCP journey. This page covers its hosted endpoint (https://phion.systems/mcp/task?phion_source=mcp_registry).

Is the PHION Task Router MCP server safe to use?

PHION Task Router 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 PHION Task Router MCP server expose?

PHION Task Router exposes 4 tools: find_or_quote_task, authorize_and_execute_selected_task, verify_or_explain_result, find_best_service_for_task. Their descriptions and schemas cost roughly 351 tokens of context every time the server is loaded.

Does the PHION Task Router MCP server require authentication?

No. We connected to PHION Task Router without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the PHION Task Router MCP server still maintained?

PHION Task Router is still listed as active in the MCP registry. We last reached this channel on 21 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 PHION Task Router MCP server?

VerifyMCP ran 13 checks on PHION Task Router, 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.