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

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

Available components

0 this week 25 Trust /100

Last scanned (22 hours ago)

Scores higher than 10% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

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 & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (5)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (6)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

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.

  • 11 Nov 26 −54
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 +13
    • Stability: fail → 0.97 functional
  • 6 Nov 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
  • 4 Nov 26 −5

    No change was recorded against any check on this day. Stability & Change Management went from 39 to 6.

  • 2 Nov 26 +3

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 39.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 15 to 20.

  • 10 Oct 26 0
    • Stability: 0.80 → fail ▼ security
    • A breaking change shipped without a version bump: still 1.0.2 ▼ security
    • Tool “accessibility_contrast_calculator” was removed ▼ security
    • Tool “data_compatibility_checker” was removed ▼ security
    • Tool “merchant_contract_regression_report” was removed ▼ security
    • Tool “public_catalog_offer_evidence” was removed ▼ security
    • Tool “x402_challenge_decode” was removed ▼ security
    • Tool “base_finality_snapshot” dropped its output schema ▼ functional
    • Tool “base_network_snapshot” dropped its output schema ▼ functional
    • Tool “base_nft_owner” dropped its output schema ▼ functional
    • Tool “base_token_metadata” dropped its output schema ▼ functional
    • Tool “base_transaction_outcome” dropped its output schema ▼ functional
    • Tool “base_wallet_snapshot” dropped its output schema ▼ functional
    • Tool “company_evidence_pack” dropped its output schema ▼ functional
    • Tool “foundry_outcome_router” dropped its output schema ▼ functional
    • Tool “machine_economy_changes_since” dropped its output schema ▼ functional
    • Tool “page_fingerprint” dropped its output schema ▼ functional
    • Tool “page_json_ld” dropped its output schema ▼ functional
    • Tool “page_links” dropped its output schema ▼ functional
    • Tool “page_markdown” dropped its output schema ▼ functional
    • Tool “page_metadata” dropped its output schema ▼ functional
    • Tool “page_tables” dropped its output schema ▼ functional
    • Tool “x402_endpoint_health” dropped its output schema ▼ functional
    • Tool “x402_endpoint_preflight” dropped its output schema ▼ functional
    • Tool “x402_metadata_drift” dropped its output schema ▼ functional
    • Tool coverage: 63% → 88% ▲ functional
    • New tool “batch_page_fingerprint” functional
    • New tool “website_evidence_pack” functional
    • New tool “x402_merchant_readiness_audit” functional
    • Tool “company_evidence_pack” changed its title: Company Evidence Pack → Company KYB & Sanctions Check cosmetic
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://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 Oct 2026 16 Jan 2027 RSA 2048 SHA256-RSA 6a477c9ccc7692571b2f107639eea27fd27
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. DS published 19718 13 Verified
zfinia.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 503
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 HTTP error 503
http (plaintext) http://api.zfinia.com/mcp HTTPS enforced 308 https://api.zfinia.com/mcp
MCP tools · 21 exposed · ~3,433 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
base_finality_snapshot ~85

How settled is Base right now? Returns the latest and finalized block heights, how many confirmations the finalized head trails by, and both timestamps. Lets an agent decide whether a transaction is safe to treat as done, instead of guessing a confirmation count. Pay 4000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

base_network_snapshot ~105

Is Base ready to transact right now? One call returns the current block height, gas price in wei and how many seconds old the chain head is, all read at the same block. Refuses before payment if the endpoint is on the wrong chain or its head is stale, so you are never charged for a reading that is quietly out of date. Pay 4000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

base_nft_owner ~109

Who owns this Base ERC721 token right now? Returns the current owner address at a pinned block. A token with no owner is refused before payment rather than returned as the zero address, which a caller could otherwise mistake for a real holder. Pay 4000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

NameTypeReqDescription
contractstringyesERC721 contract address.
token_idstringyesToken id as a decimal string.

No output schema declared.

No examples provided.

base_token_metadata ~112

Read a Base token name, symbol, decimals and total supply in one call. Handles tokens that return a bytes32 name or symbol instead of a string, which is the case that breaks naive decoders. Fields the contract does not implement come back null and are listed, rather than guessed at. Refuses an address with no contract. Pay 6000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

NameTypeReqDescription
tokenstringyesToken contract address.

No output schema declared.

No examples provided.

base_transaction_outcome ~107

Did my Base transaction work and what did it cost? One call returns success or reverted, gas used, effective gas price, the fee in wei and in exact decimal ETH, confirmations behind the head, sender, recipient, value and log count. Pending and unknown hashes get a definite answer rather than an error. Pay 6000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

NameTypeReqDescription
hashstringyesTransaction hash.

No output schema declared.

No examples provided.

base_wallet_snapshot ~127

Read a Base wallet native ETH balance and up to five ERC20 token balances at one pinned block. Separate balance lookups each answer at whatever height they happened to see, so they cannot be compared; these are all read at the same block and the block is in the response. Replaces six calls with one. Pay 8000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

NameTypeReqDescription
tokensarray–Up to five ERC20 contract addresses to read balances for.
walletstringyesWallet address to read.

No output schema declared.

No examples provided.

batch_page_fingerprint ~151

Watch up to ten reviewed public pages in one call. Supply the previous text hashes and it returns which pages actually changed, not ten hashes for you to compare. Hashes both the raw HTML and the visible text, so markup churn can be told from a real content change. A page that cannot be fetched is named individually and does not fail the batch. Pay 60000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

NameTypeReqDescription
baselineobject–Optional map of url to the text_sha256 you last saw. Without it every page reports no_baseline.
urlsarrayyesUp to 10 URLs on reviewed public origins.

No output schema declared.

No examples provided.

company_evidence_pack ~169

Company enrichment and KYB data for due diligence by domain: verify a counterparty, supplier or vendor before outreach, onboarding or payment. Returns firmographics (legal name, LEI, SEC CIK, industry, HQ, founded, employees), domain intelligence (age, email provider, SPF/DMARC), public role emails, socials, plus OFAC SDN and EU sanctions screening. Source-cited; unknowns null. Company data only, not personal contacts or compliance clearance. Unresolvable domains not charged. Pay 60000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

NameTypeReqDescription
domainstringyesCompany website domain or URL, e.g. "stripe.com" or "https://www.stripe.com/about".

No output schema declared.

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.

No output schema declared.

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.

No output schema declared.

No examples provided.

page_fingerprint ~169

Fetch a reviewed public page and return SHA-256 hashes of both the raw HTML and the visible text, with byte and character counts. Two hashes because they answer different questions: the HTML hash moves when anything at all changes, the text hash moves only when the content a reader would notice does. Pay 4000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

NameTypeReqDescription
urlstringyesHTTPS URL on a reviewed public origin. Permitted origins: https://docs.python.org, https://developer.mozilla.org, https://en.wikipedia.org, https://www.cisa.gov, https://www.sec.gov, https://home.tre…

No output schema declared.

No examples provided.

page_json_ld ~164

Fetch a reviewed public page and return every JSON-LD structured-data block it declares, parsed. No script is executed. A block that is malformed is reported as a named warning rather than being silently dropped, so a caller can tell an empty page from a broken one. Pay 5000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

NameTypeReqDescription
urlstringyesHTTPS URL on a reviewed public origin. Permitted origins: https://docs.python.org, https://developer.mozilla.org, https://en.wikipedia.org, https://www.cisa.gov, https://www.sec.gov, https://home.tre…

No output schema declared.

No examples provided.

page_links ~163

Fetch a reviewed public page and return its links with resolved absolute URLs and anchor text, the canonical URL, the declared meta robots directive, and how many links leave the host. Relative hrefs are resolved against the page, so a caller never has to guess a base. Pay 4000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

NameTypeReqDescription
urlstringyesHTTPS URL on a reviewed public origin. Permitted origins: https://docs.python.org, https://developer.mozilla.org, https://en.wikipedia.org, https://www.cisa.gov, https://www.sec.gov, https://home.tre…

No output schema declared.

No examples provided.

page_markdown ~185

Fetch a reviewed public page and return its readable content as Markdown, with headings and list structure preserved. Script, style and template content is removed, and nav and aside elements plus anything marked role="navigation" are excluded from the text. Returns the licence and creator, because this content is reusable only on those terms. Truncation at any bound is reported, never silent. Pay 6000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

NameTypeReqDescription
urlstringyesHTTPS URL on a reviewed public origin. Permitted origins: https://docs.python.org, https://developer.mozilla.org, https://en.wikipedia.org, https://www.cisa.gov, https://www.sec.gov, https://home.tre…

No output schema declared.

No examples provided.

page_metadata ~162

Fetch a reviewed public page and return its title, every meta and Open Graph tag, and the canonical URL. No JavaScript is executed and no script content is read. Returns the licence and creator for the content alongside it, so reuse terms travel with the result. Pay 4000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

NameTypeReqDescription
urlstringyesHTTPS URL on a reviewed public origin. Permitted origins: https://docs.python.org, https://developer.mozilla.org, https://en.wikipedia.org, https://www.cisa.gov, https://www.sec.gov, https://home.tre…

No output schema declared.

No examples provided.

page_tables ~164

Fetch a reviewed public page and return its HTML tables as arrays of rows and cells. Bounded to ten tables, fifty rows each and twenty cells per row, and every bound that is reached is named in the warnings so a truncated table is never mistaken for a short one. Pay 6000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

NameTypeReqDescription
urlstringyesHTTPS URL on a reviewed public origin. Permitted origins: https://docs.python.org, https://developer.mozilla.org, https://en.wikipedia.org, https://www.cisa.gov, https://www.sec.gov, https://home.tre…

No output schema declared.

No examples provided.

website_evidence_pack ~229

Everything a reviewed public page declares, in one call and one fetch: title, meta and Open Graph, canonical, robots directive, JSON-LD with its schema.org types, resolved links with an external count, tables, content fingerprints, and readable Markdown. Replaces six separate extraction calls, and adds the cross-checks none of them can make alone — a canonical that disagrees with the URL you asked for, a page declaring noindex, missing structured data. Pay 50000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

NameTypeReqDescription
include_markdownboolean–Set false to omit the Markdown body and keep the response small. Defaults to true.
urlstringyesHTTPS URL on a reviewed public origin. Permitted origins: https://docs.python.org, https://developer.mozilla.org, https://en.wikipedia.org, https://www.cisa.gov, https://www.sec.gov, https://home.tre…

No output schema declared.

No examples provided.

x402_endpoint_health ~158

Is this paid endpoint answering right now? Returns whether it serves a payment challenge, how many well-formed priced offers it carries, which warnings would actually break a payment as opposed to merely making the call harder to construct, and a single payable_now flag. Reports only what was observed; it makes no judgement about the seller. Pay 4000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

NameTypeReqDescription
bodyobject–Optional JSON body to send with a POST probe.
methodstring–Method to probe with. Defaults to GET.
urlstringyesHTTPS URL of an x402 endpoint on a reviewed origin. Credentials, ports and fragments are refused.

No output schema declared.

No examples provided.

x402_endpoint_preflight ~163

Find out what an x402 endpoint will charge before you pay it. Probes the endpoint, reads the challenge from the header or the body, and returns the decoded price, network, asset and payTo plus the declared input and output schemas. Never sends a payment. Only reviewed origins are reachable, and a redirect is refused rather than followed. Pay 4000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

NameTypeReqDescription
bodyobject–Optional JSON body to send with a POST probe.
methodstring–Method to probe with. Defaults to GET.
urlstringyesHTTPS URL of an x402 endpoint on a reviewed origin. Credentials, ports and fragments are refused.

No output schema declared.

No examples provided.

x402_merchant_readiness_audit ~188

Is this merchant safe to depend on? Audits up to ten x402 endpoints in one call and returns a verdict — ready, partially ready or not ready — with the specific blockers. Checks each endpoint serves a payable challenge with well-formed terms and a declared input schema, and adds the cross-endpoint check no single probe can make: whether every endpoint pays the same recipient. Never pays anything. Pay 25000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

NameTypeReqDescription
endpointsarrayyesUp to 10 endpoints. Give a descriptor with the request that endpoint actually needs — probing a paid API with an empty POST reports it unpayable when it is merely undocumented here.
expected_pay_tostring–Optional. The recipient you expect every endpoint to pay; a difference becomes a blocker.

No output schema declared.

No examples provided.

x402_metadata_drift ~179

Did this paid endpoint change its terms since you last looked? Give it a previous challenge as the baseline and it returns every difference: price changes with old and new amounts, offers added or removed, a protocol version change, and a payee_changed flag when a new recipient address appears. Never pays the endpoint. Pay 6000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

NameTypeReqDescription
baselineobjectyesA challenge object from an earlier preflight or decode, used as the comparison point.
bodyobject–Optional JSON body to send with a POST probe.
methodstring–Method to probe with. Defaults to GET.
urlstringyesHTTPS URL of an x402 endpoint on a reviewed origin. Credentials, ports and fragments are refused.

No output schema declared.

No examples provided.

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'
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 25 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 21 tools: company_evidence_pack, machine_economy_changes_since, foundry_outcome_router, x402_endpoint_preflight, x402_endpoint_health, and 16 more. Their descriptions and schemas cost roughly 3,433 tokens of context every time the server is loaded.

Does the zFinia Intelligence MCP server require authentication?

Its publisher declares no required credentials for zFinia Intelligence. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

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

VerifyMCP ran 5 checks on zFinia Intelligence, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about zFinia Intelligence: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.