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 Agent Trust Infrastructure

REMOTE · PHION.SYSTEMS · SCANNED SEP 25

118 agent services with free discovery, intent, x402 terms and signed verification.

Available components

+4 this week 66 Trust /100
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 Security63
Transport & Reachability100
Schema Quality & AI Usability58
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 5964 tokens (~48/item across 124 items; 124 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage72
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 2% of tool parameters carry a description.Partial
  • Structured output schemas are declared (58% of tools); any adoption earns full credit.Pass
Tool Safety88
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 1 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "duplicate_charge_detector" implies "charge" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 124 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
Install

How do I install the PHION Agent Trust Infrastructure MCP server?

PHION Agent Trust Infrastructure is a hosted endpoint at https://phion.systems/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 · phion.systems

# add to Claude Code
claude mcp add --transport http systems-phion-evidence-engine 'https://phion.systems/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "systems-phion-evidence-engine": {
      "url": "https://phion.systems/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "systems-phion-evidence-engine": {
      "type": "http",
      "url": "https://phion.systems/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.systems-phion-evidence-engine]
url = "https://phion.systems/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "systems-phion-evidence-engine": {
      "type": "remote",
      "url": "https://phion.systems/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add systems-phion-evidence-engine --url 'https://phion.systems/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  systems-phion-evidence-engine:
    url: "https://phion.systems/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "systems-phion-evidence-engine": {
      "Transport": "http",
      "Url": "https://phion.systems/mcp"
    }
  }
}
# add to Vellum
assistant mcp add systems-phion-evidence-engine -t streamable-http -u 'https://phion.systems/mcp'
// mcp.json
{
  "mcpServers": {
    "systems-phion-evidence-engine": {
      "type": "http",
      "url": "https://phion.systems/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 25 Sept 26 −1
    • MCP protocol: pass → fail ▼ functional
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
    • Server version: 1.49.4 → 1.49.6 functional
    • Server version: 1.49.3 → 1.49.4 functional
    • Server version: 1.49.0 → 1.49.3 functional
  • 24 Sept 26 +1
    • Server version: 1.46.2 → 1.46.4 functional
  • 23 Sept 26 0
    • Server version: 1.46.1 → 1.46.2 functional
    • Server version: 1.46.0 → 1.46.1 functional
    • Server version: 1.45.0 → 1.46.0 functional
  • 22 Sept 26 +1
    • Schema quality: 4804 → 5964 ▼ functional
    • Tool coverage: 45% → 58% ▲ functional
    • Tool coverage: 45% → 50% ▲ functional
    • Server version: 1.44.0 → 1.45.0 functional
    • Server version: 1.39.0 → 1.44.0 functional
    • Server version: 1.37.0 → 1.39.0 functional
    • New tool “a2a_transaction_bridge” functional
    • New tool “agent_economic_graph” functional
    • New tool “ap2_mandate_bridge” functional
    • New tool “automated_dispute_bundle” functional
    • New tool “autonomous_procurement” functional
    • New tool “cross_protocol_receipt” functional
    • New tool “delegated_spend_policy” functional
    • New tool “dynamic_service_pricing” functional
    • New tool “erc8004_identity_evidence” functional
    • New tool “erc8004_reputation_intelligence” functional
    • New tool “market_demand_predictor” functional
    • New tool “mcp_transaction_gateway” functional
    • New tool “multi_agent_escrow” functional
    • New tool “price_discovery_engine” functional
    • New tool “proof_of_service” functional
    • New tool “reputation_update_receipt” functional
    • New tool “service_gap_detector” functional
    • New tool “sla_risk_predictor” functional
    • New tool “transaction_recovery_v2” functional
    • New tool “agent_behavior_fingerprint” functional
    • New tool “capability_benchmark” functional
    • New tool “capability_verification” functional
    • New tool “economic_loop_detector” functional
    • New tool “payment_optimizer” functional
    • New tool “provider_quality_predictor” functional
    • New tool “sybil_reputation_guard” functional
    • New tool “transaction_risk_score” functional
    • New tool “trust_anomaly_detector” functional
    • New tool “x402_v2_router” functional
  • 21 Sept 26 +2
    • Schema quality: 57 → 50 ▲ functional
    • Tool coverage: 31% → 45% ▲ functional
    • Tool coverage: 31% → 39% ▲ functional
    • MCP protocol: fail → pass ▲ functional
    • MCP protocol version: 2025-06-18 → 2026-07-28 functional
    • Server version: 1.35.0 → 1.37.0 functional
    • Server version: 1.33.0 → 1.35.0 functional
    • Server version: 1.32.2 → 1.33.0 functional
    • Server version: 1.32.3 → 1.32.2 functional
    • New tool “tool_result_schema_validator” functional
    • New tool “agent_memory_provenance” functional
    • New tool “agent_rate_limit_negotiator” functional
    • New tool “agent_session_continuity” functional
    • New tool “cross_agent_receipt_bundle” functional
    • New tool “delegated_credential_guard” functional
    • New tool “execution_cost_estimator” functional
    • New tool “payment_delivery_atomicity” functional
    • New tool “service_failover_selector” functional
    • New tool “task_lease_guard” functional
    • New tool “agent_approval_relay” functional
    • New tool “capability_negotiation_preflight” functional
    • New tool “durable_agent_task” functional
    • New tool “mcp_2026_compatibility_gateway” functional
    • New tool “mcp_a2a_task_bridge” functional
    • New tool “mcp_catalog_cache_guard” functional
    • New tool “oauth_issuer_binding_evidence” functional
    • New tool “quote_freshness_guard” functional
    • New tool “task_cancel_assurance” functional
    • New tool “task_checkpoint_evidence” functional
  • 20 Sept 26 0
    • Server version: 1.32.0 → 1.32.3 functional
  • 19 Sept 26 +1
    • Tool “company_enrichment_evidence” rewrote its description, which is the text the model reads security
    • Tool “contact_enrichment_evidence” rewrote its description, which is the text the model reads security
    • Tool “person_enrichment_evidence” rewrote its description, which is the text the model reads security
    • Schema quality: 50 → 57 ▼ functional
    • Server version: 1.31.1 → 1.32.0 functional
    • “company_enrichment_evidence” added an optional parameter “birth_date” cosmetic
    • “company_enrichment_evidence” added an optional parameter “contact” cosmetic
    • “company_enrichment_evidence” added an optional parameter “country” cosmetic
    • “company_enrichment_evidence” added an optional parameter “email” cosmetic
    • “company_enrichment_evidence” added an optional parameter “email_hash” cosmetic
    • “company_enrichment_evidence” added an optional parameter “entity” cosmetic
    • “company_enrichment_evidence” added an optional parameter “first_name” cosmetic
    • “company_enrichment_evidence” added an optional parameter “identifier” cosmetic
    • “company_enrichment_evidence” added an optional parameter “input” cosmetic
    • “company_enrichment_evidence” added an optional parameter “last_name” cosmetic
    • “company_enrichment_evidence” added an optional parameter “lid” cosmetic
    • “company_enrichment_evidence” added an optional parameter “locality” cosmetic
    • “company_enrichment_evidence” added an optional parameter “minimum_likelihood” cosmetic
    • “company_enrichment_evidence” added an optional parameter “pdl_id” cosmetic
    • “company_enrichment_evidence” added an optional parameter “person” cosmetic
    • “company_enrichment_evidence” added an optional parameter “phone” cosmetic
    • “company_enrichment_evidence” added an optional parameter “postal_code” cosmetic
    • “company_enrichment_evidence” added an optional parameter “query” cosmetic
    • “company_enrichment_evidence” added an optional parameter “region” cosmetic
    • “company_enrichment_evidence” added an optional parameter “school” cosmetic
    • “company_enrichment_evidence” added an optional parameter “street_address” cosmetic
    • “company_enrichment_evidence” added an optional parameter “subject” cosmetic
    • “contact_enrichment_evidence” added an optional parameter “birth_date” cosmetic
    • “contact_enrichment_evidence” added an optional parameter “contact” cosmetic
    • “contact_enrichment_evidence” added an optional parameter “country” cosmetic
    • “contact_enrichment_evidence” added an optional parameter “email_hash” cosmetic
    • “contact_enrichment_evidence” added an optional parameter “entity” cosmetic
    • “contact_enrichment_evidence” added an optional parameter “first_name” cosmetic
    • “contact_enrichment_evidence” added an optional parameter “identifier” cosmetic
    • “contact_enrichment_evidence” added an optional parameter “input” cosmetic
    • “contact_enrichment_evidence” added an optional parameter “last_name” cosmetic
    • “contact_enrichment_evidence” added an optional parameter “lid” cosmetic
    • “contact_enrichment_evidence” added an optional parameter “locality” cosmetic
    • “contact_enrichment_evidence” added an optional parameter “pdl_id” cosmetic
    • “contact_enrichment_evidence” added an optional parameter “person” cosmetic
    • “contact_enrichment_evidence” added an optional parameter “phone” cosmetic
    • “contact_enrichment_evidence” added an optional parameter “postal_code” cosmetic
    • “contact_enrichment_evidence” added an optional parameter “query” cosmetic
    • “contact_enrichment_evidence” added an optional parameter “region” cosmetic
    • “contact_enrichment_evidence” added an optional parameter “school” cosmetic
    • “contact_enrichment_evidence” added an optional parameter “street_address” cosmetic
    • “contact_enrichment_evidence” added an optional parameter “subject” cosmetic
    • “contact_enrichment_evidence” added an optional parameter “ticker” cosmetic
    • “contact_enrichment_evidence” added an optional parameter “website” cosmetic
    • “person_enrichment_evidence” added an optional parameter “birth_date” cosmetic
    • “person_enrichment_evidence” added an optional parameter “contact” cosmetic
    • “person_enrichment_evidence” added an optional parameter “country” cosmetic
    • “person_enrichment_evidence” added an optional parameter “email_hash” cosmetic
    • “person_enrichment_evidence” added an optional parameter “entity” cosmetic
    • “person_enrichment_evidence” added an optional parameter “first_name” cosmetic
    • “person_enrichment_evidence” added an optional parameter “identifier” cosmetic
    • “person_enrichment_evidence” added an optional parameter “input” cosmetic
    • “person_enrichment_evidence” added an optional parameter “last_name” cosmetic
    • “person_enrichment_evidence” added an optional parameter “lid” cosmetic
    • “person_enrichment_evidence” added an optional parameter “locality” cosmetic
    • “person_enrichment_evidence” added an optional parameter “pdl_id” cosmetic
    • “person_enrichment_evidence” added an optional parameter “person” cosmetic
    • “person_enrichment_evidence” added an optional parameter “phone” cosmetic
    • “person_enrichment_evidence” added an optional parameter “postal_code” cosmetic
    • “person_enrichment_evidence” added an optional parameter “query” cosmetic
    • “person_enrichment_evidence” added an optional parameter “region” cosmetic
    • “person_enrichment_evidence” added an optional parameter “school” cosmetic
    • “person_enrichment_evidence” added an optional parameter “street_address” cosmetic
    • “person_enrichment_evidence” added an optional parameter “subject” cosmetic
    • “person_enrichment_evidence” added an optional parameter “ticker” cosmetic
    • “person_enrichment_evidence” added an optional parameter “website” cosmetic
    • “company_enrichment_evidence” reworded the description of “company” cosmetic
    • “contact_enrichment_evidence” reworded the description of “company” cosmetic
    • “person_enrichment_evidence” reworded the description of “company” cosmetic
  • 17 Sept 26 +1

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

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 25 Sept 2026 · Probed https://phion.systems/mcp

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=YE2,O=Let's Encrypt,C=US 30 Jul 2026 28 Oct 2026 ECDSA 256 ECDSA-SHA384 64d09cefb1b3a722bb9f05fcaf93ae899ed
SANs: phion.systems, www.phion.systems
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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. present 9634 8 Verified
phion.systems. 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
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 Verified 200
http (plaintext) http://phion.systems/mcp HTTPS enforced 301 https://phion.systems/mcp
MCP tools · 124 exposed · ~5,964 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
a2a_transaction_bridge ~42

Bind an A2A task to a transaction without silently transferring authority.; 0.004 USDC. Deterministic, evidence-bounded and signed.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

abandoned_tool_detector ~44

Require stale success plus multiple independent failed probes before classifying likely abandonment; 0.003 USDC.

NameTypeReqDescription
policyobjectyes–
toolobjectyes–

No output schema declared.

No examples provided.

agent_approval_relay ~22

Agent Approval Relay; deterministic signed assessment over supplied input.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

agent_behavior_fingerprint ~42

Create a privacy-minimized behavioral commitment without retaining payloads or raw identifiers.; 0.003 USDC. Deterministic, evidence-bounded and signed.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

agent_budget_guard ~28

Enforce per-call, task, session and period budgets; 0.002 USDC.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

agent_economic_graph ~40

Build privacy-bounded economic relationships only from supplied nodes and edges.; 0.005 USDC. Deterministic, evidence-bounded and signed.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

agent_memory_provenance ~23

Agent Memory Provenance; deterministic signed assessment over supplied input.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

agent_rate_limit_negotiator ~25

Agent Rate Limit Negotiator; deterministic signed assessment over supplied input.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

agent_reputation_evidence ~57

Evidence-bounded agent reputation assessment with confidence, coverage, provenance limitations and a signed receipt; 0.005 USDC.

NameTypeReqDescription
evidencearray––
signalsobject––
subjectobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

agent_session_continuity ~23

Agent Session Continuity; deterministic signed assessment over supplied input.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

agent_task_handoff_receipt ~27

Sign a bounded agent-task handoff; 0.003 USDC.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

ap2_mandate_bridge ~42

Map mandate fields for review without advertising unsupported AP2 production authorization.; 0.004 USDC. Deterministic, evidence-bounded and signed.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

attest ~44

x402 paid signed JSON attestation; 0.001 USDC on Base.

NameTypeReqDescription
content–yes–
sourcesarray––
ttl_secondsinteger––

No output schema declared.

No examples provided.

automated_dispute_bundle ~37

Assemble failure evidence and recommend resolution without executing refunds.; 0.005 USDC. Deterministic, evidence-bounded and signed.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

autonomous_procurement ~37

Recommend a verified eligible provider under a mandate without purchasing.; 0.005 USDC. Deterministic, evidence-bounded and signed.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

capability_benchmark ~42

Measure reproducible success, latency and cost from versioned evidence-bound benchmark cases.; 0.004 USDC. Deterministic, evidence-bounded and signed.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

capability_negotiation_preflight ~25

Capability Negotiation Preflight; deterministic signed assessment over supplied input.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

capability_verification ~35

Separate claimed capabilities from independently evidenced successful demonstrations.; 0.003 USDC. Deterministic, evidence-bounded and signed.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

company_enrichment_evidence ~259

Company enrichment with free input preflight, provider attribution and signed evidence; 0.005 USDC.

NameTypeReqDescription
birth_datestring––
company––Company name or nested input object
contactobject––
countrystring––
emailstring––
email_hashstring––
entityobject––
first_namestring––
identifierstring–Email, profile URL, phone, company domain, ticker or name; interpreted by service
inputobject––
last_namestring––
lidstring––
localitystring––
locationstring––
minimum_likelihoodinteger––
namestring––
pdl_idstring––
personobject––
phonestring––
postal_codestring––
profilestring––
queryobject––
regionstring––
schoolstring––
street_addressstring––
subjectobject––
tickerstring––
websitestring––

No output schema declared.

No examples provided.

concurrency_guard ~94

Fail closed unless capacity counter is fresh and the request carries a lease plus idempotency binding; 0.002 USDC.

NameTypeReqDescription
active_slotsintegeryes–
counter_observed_atintegeryes–
idempotency_keystringyes–
lease_idstringyes–
lease_valid_untilintegeryes–
policyobjectyes–
requested_slotsintegeryes–

No output schema declared.

No examples provided.

conflict_resolution ~49

Resolve or abstain; every candidate must bind source, value hash, observation time and bounded confidence; 0.003 USDC.

NameTypeReqDescription
candidatesarrayyes–
policyobjectyes–

No output schema declared.

No examples provided.

contact_enrichment_evidence ~260

Business-contact enrichment with free input preflight, identity limitations and signed receipt; 0.007 USDC.

NameTypeReqDescription
birth_datestring––
company––Company name or nested input object
contactobject––
countrystring––
emailstring––
email_hashstring––
entityobject––
first_namestring––
identifierstring–Email, profile URL, phone, company domain, ticker or name; interpreted by service
inputobject––
last_namestring––
lidstring––
localitystring––
locationstring––
minimum_likelihoodinteger––
namestring––
pdl_idstring––
personobject––
phonestring––
postal_codestring––
profilestring––
queryobject––
regionstring––
schoolstring––
street_addressstring––
subjectobject––
tickerstring––
websitestring––

No output schema declared.

No examples provided.

context_provenance_labeler ~29

Hash and label context integrity, confidentiality and source; 0.002 USDC.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

counterparty_risk_preflight ~63

Deterministic counterparty policy preflight using supplied reputation evidence and transaction limits; 0.003 USDC.

NameTypeReqDescription
policyobject––
reputationobject––
subjectobjectyes–
transactionobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

cross_agent_receipt_bundle ~23

Cross-Agent Receipt Bundle; deterministic signed assessment over supplied input.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

cross_protocol_receipt ~35

Bundle consistent transaction commitments across multiple protocols.; 0.004 USDC. Deterministic, evidence-bounded and signed.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

data_egress_preflight ~47

Inspect outbound agent data and destination before transmission; 0.002 USDC.

NameTypeReqDescription
destinationobjectyes–
payload–yes–
policyobject––

Structured output declared, but exposes no named fields.

No examples provided.

data_freshness_certificate ~52

Certify freshness only when timestamp is bound to source URI and a 64-hex content hash; 0.002 USDC.

NameTypeReqDescription
dataobjectyes–
policyobjectyes–

No output schema declared.

No examples provided.

delegated_credential_guard ~22

Delegated Credential Guard; deterministic signed assessment over supplied input.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

delegated_spend_policy ~42

Fail closed when delegated authority, per-call limit or remaining budget is insufficient.; 0.003 USDC. Deterministic, evidence-bounded and signed.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

delegation_scope_guard ~48

Least-privilege guard for agent-to-agent delegation scope, destinations, budget and expiry; 0.003 USDC.

NameTypeReqDescription
delegationobjectyes–
policyobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

delivery_evidence ~47

Bind successful delivery to transaction, request and matching 64-hex expected/observed content hashes without echoing content; 0.003 USDC.

NameTypeReqDescription
deliveryobjectyes–

No output schema declared.

No examples provided.

dependency_provenance_assessment ~51

Fail closed on empty dependency sets or absent registry policy; distinguish digest declarations from verified provenance; 0.003 USDC.

NameTypeReqDescription
dependenciesarrayyes–
policyobjectyes–

No output schema declared.

No examples provided.

document_to_verified_json ~50

Public text, HTML, JSON or XML normalized to source-backed JSON; no OCR; 0.010 USDC.

NameTypeReqDescription
expected_fieldsarray––
source_urlsarrayyes–

No output schema declared.

No examples provided.

domain_ownership_evidence ~52

Require a fresh domain-bound DNS-01/HTTP-01 challenge and separate control from legal ownership; 0.003 USDC.

NameTypeReqDescription
domainstringyes–
evidenceobjectyes–

No output schema declared.

No examples provided.

duplicate_charge_detector ~36

Detect repeated transaction hashes, payment identifiers and idempotent intents; 0.003 USDC.

NameTypeReqDescription
chargesarrayyes–

No output schema declared.

No examples provided.

durable_agent_task ~20

Durable Agent Task; deterministic signed assessment over supplied input.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

dynamic_service_pricing ~39

Propose a capped shadow price without changing the live catalog.; 0.004 USDC. Deterministic, evidence-bounded and signed.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

economic_loop_detector ~39

Detect self-transfer and reciprocal economic patterns without presenting correlation as fraud.; 0.004 USDC. Deterministic, evidence-bounded and signed.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

entity_enrichment_evidence ~52

Source-bounded entity field coverage with explicit missing facts; 0.008 USDC.

NameTypeReqDescription
expected_fieldsarray––
source_urlsarrayyes–
subjectobject––

No output schema declared.

No examples provided.

erc8004_identity_evidence ~46

Bind an ERC-8004 registry identity to evidence while separating registration from ownership.; 0.004 USDC. Deterministic, evidence-bounded and signed.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

erc8004_reputation_intelligence ~43

Aggregate diverse verified reputation observations with low-sample abstention.; 0.004 USDC. Deterministic, evidence-bounded and signed.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

execution_cost_estimator ~22

Execution Cost Estimator; deterministic signed assessment over supplied input.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

fetch_evidence ~45

Independently fetch bounded public evidence with redirect/DNS/connected-address SSRF checks, hashes and injection screening; 0.004 USDC.

NameTypeReqDescription
urlstringyes–

No output schema declared.

No examples provided.

human_approval_policy ~29

Classify an action as automatic, approval-required or denied; 0.002 USDC.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

idempotency_replay_guard ~31

Detect safe replays and conflicting idempotency-key reuse; 0.002 USDC.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

index_feed ~53

Canonical catalog snapshot or digest-based delta with exact HTTP/MCP records, PHION Execute templates and signed evidence; 0.005 USDC.

NameTypeReqDescription
mode–yes–
since_snapshot_sha256string––

No output schema declared.

No examples provided.

inspect_agent ~50

Pre-payment agent inspection across x402, A2A, ERC-8004, OpenAPI and MCP; failed inspections are not charged; 0.009 USDC.

NameTypeReqDescription
urlstringyes–

No output schema declared.

No examples provided.

inter_agent_policy_evaluator ~46

Require policy identity, subject, action, lifetime and valid decisions; compute the restrictive cap and shared actions; 0.003 USDC.

NameTypeReqDescription
policiesarrayyes–

No output schema declared.

No examples provided.

interrupted_task_recovery ~62

Resume only when task/checkpoint identity, sequence, deadline, attempt budget, idempotency and side effects are explicit; 0.003 USDC.

NameTypeReqDescription
checkpointobjectyes–
policyobjectyes–
taskobjectyes–

No output schema declared.

No examples provided.

Common questions

What is the PHION Agent Trust Infrastructure MCP server?

PHION Agent Trust Infrastructure is an MCP server listed in the public MCP registry as systems.phion/evidence-engine. 118 agent services with free discovery, intent, x402 terms and signed verification. This page covers its hosted endpoint (https://phion.systems/mcp).

Is the PHION Agent Trust Infrastructure MCP server safe to use?

PHION Agent Trust Infrastructure scores 66 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 Agent Trust Infrastructure MCP server expose?

PHION Agent Trust Infrastructure exposes 124 tools: phion_execute, index_feed, preflight, try_service, schema_normalize_free, and 119 more. Their descriptions and schemas cost roughly 5,964 tokens of context every time the server is loaded.

Does the PHION Agent Trust Infrastructure MCP server require authentication?

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

Is the PHION Agent Trust Infrastructure MCP server still maintained?

PHION Agent Trust Infrastructure is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.