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.

zFinia Intelligence

REMOTE · API.ZFINIA.COM · SCANNED SEP 28

Machine-economy newswire and paid changes-since for agents. MCP is challenge-handoff, not a wallet.

Available components

+1 this week 69 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 Usability52
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1401 tokens (~233/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
  • Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage80
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 30% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the zFinia Intelligence MCP server?

zFinia Intelligence is a hosted endpoint at https://api.zfinia.com/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 · api.zfinia.com

# add to Claude Code
claude mcp add --transport http com-zfinia-api-intelligence 'https://api.zfinia.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-zfinia-api-intelligence": {
      "url": "https://api.zfinia.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-zfinia-api-intelligence": {
      "type": "http",
      "url": "https://api.zfinia.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-zfinia-api-intelligence]
url = "https://api.zfinia.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-zfinia-api-intelligence": {
      "type": "remote",
      "url": "https://api.zfinia.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-zfinia-api-intelligence --url 'https://api.zfinia.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-zfinia-api-intelligence:
    url: "https://api.zfinia.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-zfinia-api-intelligence": {
      "Transport": "http",
      "Url": "https://api.zfinia.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-zfinia-api-intelligence -t streamable-http -u 'https://api.zfinia.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-zfinia-api-intelligence": {
      "type": "http",
      "url": "https://api.zfinia.com/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.

  • 28 Sept 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
  • 27 Sept 26 +1

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

  • 26 Sept 26 0
    • Endpoint reachability: not serving MCP → reachable ▲ functional
  • 25 Sept 26 +43
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 −43
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.47 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 23 Sept 26 +2
    • Tool “accessibility_contrast_calculator” rewrote its description, which is the text the model reads security
    • Tool “data_compatibility_checker” rewrote its description, which is the text the model reads security
    • Tool “machine_economy_changes_since” rewrote its description, which is the text the model reads security
    • Tool “merchant_contract_regression_report” rewrote its description, which is the text the model reads security
    • Tool “public_catalog_offer_evidence” rewrote its description, which is the text the model reads security
    • Schema quality: fair → good functional
  • 22 Sept 26 −2
    • Tool “accessibility_contrast_calculator” rewrote its description, which is the text the model reads security
    • Tool “data_compatibility_checker” rewrote its description, which is the text the model reads security
    • Tool “machine_economy_changes_since” rewrote its description, which is the text the model reads security
    • Tool “merchant_contract_regression_report” rewrote its description, which is the text the model reads security
    • Tool “public_catalog_offer_evidence” rewrote its description, which is the text the model reads security
    • Schema quality: good → fair functional
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
    • Tool “merchant_contract_regression_report” changed its title: merchant contract regression report → Merchant Contract Regression Report cosmetic
  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 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 28 Sept 2026 · Probed https://api.zfinia.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.zfinia.com CN=YR1,O=Let's Encrypt,C=US 18 Aug 2026 16 Nov 2026 RSA 2048 SHA256-RSA 5b2f2f000dac02d53396225efe55ac78c54
SANs: api.zfinia.com
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 api.zfinia.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
zfinia.com. 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=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.zfinia.com/mcp Verified 200
http (plaintext) http://api.zfinia.com/mcp HTTPS enforced 308 https://api.zfinia.com/mcp
MCP tools · 6 exposed · ~1,052 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
accessibility_contrast_calculator ~120

Calculate WCAG 2.x sRGB contrast for one caller-supplied foreground/background pair of hex colours (#RRGGBB). Returns JSON with the contrast ratio and AA/AAA threshold booleans for normal or large text. Does not assess a whole interface, support alpha colours or certify accessibility. Pay 1000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

NameTypeReqDescription
backgroundstringyes–
foregroundstringyes–
large_textbooleanyes–
NameTypeReqDescription
contrast_rationumberyes–
large_textbooleanyes–
limitationsarrayyes–
request_idstringyesDelivery request identifier; also returned in x-foundry-request-id.
service_idstringyesCanonical service identifier.
service_versionstringyesVersion of the invoked service.
wcag_aabooleanyes–
wcag_aaabooleanyes–

No examples provided.

data_compatibility_checker ~140

Compare caller-supplied source and target flat field schemas before ingestion, migration, CI deployment or machine-to-machine handoff. Returns a deterministic JSON mismatch report with type incompatibilities, missing required fields, nullability warnings and remediation codes. Does not fetch data or validate nested schemas, data values or runtime API behaviour. Pay 3000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

NameTypeReqDescription
canonicalizationstring––
comparison_modestring––
contract_versionstring––
source_fieldsarrayyes–
target_fieldsarrayyes–
NameTypeReqDescription
assumptionsarrayyes–
canonicalizationobjectyes–
checked_source_fieldsintegeryes–
checked_target_fieldsintegeryes–
comparison_modestringyes–
compatiblebooleanyes–
contract_versionstringyes–
issue_countintegeryes–
issuesarrayyes–
limitationsarrayyes–
remediationsarrayyes–
request_idstringyesDelivery request identifier; also returned in x-foundry-request-id.
service_idstringyesCanonical service identifier.
service_versionstringyesVersion of the invoked service.

No examples provided.

foundry_outcome_router ~350

Use when you need an outcome and do not already know which zFinia utility to call. Send objective (aliases: goal, task, outcome, query) plus inputs. Top-level colour/field/html/cursor keys fold into inputs. tools/call quotes first and returns PAYMENT_REQUIRED for an already-live x402 resource at that resource's unchanged price (contrast 1000, DCC 3000, catalog-offer 100000, changes-since 10000). Batches are sequential pays on those same live rails. POST /v1/router/quote is unpaid. No URL fetching. MCP does not pay. GET /v1/router for the free contract.

NameTypeReqDescription
buyer_metadataobject–Optional non-secret buyer hints. Secret-like keys are stripped and never persisted.
evidencestring––
freshnessstring––
inputsobject–Caller-supplied facts required to produce the outcome. Do not send secrets or ask Foundry to fetch URLs.
latencystring––
max_pricestring–Optional maximum USDC atomic units the buyer will pay.
objectivestringyesOutcome the buyer needs. Foundry chooses the execution plan; do not describe supplier topology. goal, task, outcome, and query are accepted aliases. Product names, service IDs, and live routes are va…
preferred_protocolstring––
required_outputobject–Optional desired output shape or fields.
NameTypeReqDescription
economicsobjectyes–
evidenceobjectyes–
execution_idstringyes–
latency_msnumber––
limitationsarrayyes–
outcomestringyes–
planobject––
request_fingerprintstring––
resultobjectyes–
statusstringyes–
value_addobject––

No examples provided.

machine_economy_changes_since ~194

Return curated machine-economy developments covering x402 and agent commerce after a supplied cursor or since value. This delta feed includes material additions, corrections and retractions with provenance and nextCursor for caller-managed polling; an empty result is valid. No transaction feed, built-in scheduler, generic web search or exhaustive ecosystem monitoring. Pay 10000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

NameTypeReqDescription
cursorstring–Previous nextCursor (opaque or ISO-8601). Required for the paid delta unless since is set. Pass this back on the next poll.
include_high_resolutionboolean–When true, paid items include full evidence fields already present on the public newswire item.
maxItemsinteger––
sincestring–Alias of cursor. Use the previous nextCursor so only later material changes are returned.
NameTypeReqDescription
countintegeryes–
generatedAtstringyes–
highResolutionboolean––
itemsarrayyes–
marketMovementsobject––
nextCursorstringyes–
priceAtomicstring––
productstring––
request_idstringyesDelivery request identifier; also returned in x-foundry-request-id.
schemastringyes–
schemaVersionstring––
service_idstringyesCanonical service identifier.
service_versionstringyesVersion of the invoked service.
sincestringyes–
truncatedbooleanyes–
usageRightsstringyes–

No examples provided.

merchant_contract_regression_report ~130

Compare supplied baseline/current merchant API contracts for CI review. Returns a structured diff report with hashes, remediation, route/method checks, network/asset/payee policy checks, flat input/output compatibility and declared current price against the buyer maximum. No URL fetching, live or future-price guarantee, security audit or CI enforcement. Pay 50000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

NameTypeReqDescription
baselineobjectyes–
currentobjectyes–
merchant_service_idstringyes–
policyobjectyes–
NameTypeReqDescription
checked_atstringyesServer evaluation time; distinct from caller-supplied observation times.
checksarrayyes–
conclusionstringyes–
coverageobjectyes–
limitationsarrayyes–
merchant_service_idstringyes–
report_versionstringyes–
request_idstringyesDelivery request identifier; also returned in x-foundry-request-id.
security_audit_performedbooleanyes–
service_idstringyesCanonical service identifier.
service_versionstringyesVersion of the invoked service.
snapshotobjectyes–

No examples provided.

public_catalog_offer_evidence ~118

Extract schema.org Product JSON-LD structured data from caller-supplied authorized public product-page HTML. Returns deterministic normalized Product/Offer JSON, including supplied price and currency when present, with source HTML and record SHA-256 hashes. Performs no URL fetching or browser execution; hashes do not prove authenticity and supplied prices may be stale. Pay 100000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

NameTypeReqDescription
htmlstringyes–
source_urlstringyes–
NameTypeReqDescription
capability_id–yes–
evidenceobjectyes–
productobjectyes–
sourceobjectyes–
versionstringyes–

No examples provided.

Common questions

What is the zFinia Intelligence MCP server?

zFinia Intelligence is an MCP server listed in the public MCP registry as com.zfinia.api/intelligence. Machine-economy newswire and paid changes-since for agents. MCP is challenge-handoff, not a wallet. This page covers its hosted endpoint (https://api.zfinia.com/mcp).

Is the zFinia Intelligence MCP server safe to use?

zFinia Intelligence 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 zFinia Intelligence MCP server expose?

zFinia Intelligence exposes 6 tools: accessibility_contrast_calculator, data_compatibility_checker, machine_economy_changes_since, merchant_contract_regression_report, foundry_outcome_router, public_catalog_offer_evidence. Their descriptions and schemas cost roughly 1,052 tokens of context every time the server is loaded.

Does the zFinia Intelligence MCP server require authentication?

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

Is the zFinia Intelligence MCP server still maintained?

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