Is the Zfinia Intelligence MCP server down?

mcp-registry/com.zfinia.api/intelligence

degraded
Last checked 2026-10-19 16:07 UTC · handshake 998ms

As of 2026-10-19 16:07 UTC, the Zfinia Intelligence MCP server is degraded with a Glimind reliability score of 48/100 (grade D). Over the last 30 days it answered 90.1% of Glimind's liveness checks. It had 250 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
90.1%
checks observed
3,624
outages (90d)
250
tools
21

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

Install Zfinia Intelligence MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http zfinia-intelligence-mcp-server https://api.zfinia.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "zfinia-intelligence-mcp-server": {
      "type": "http",
      "url": "https://api.zfinia.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (70/100)

C (70/100): 1 error(s), 4 warning(s) across 21 tool(s); ~6,113 tokens of tool definitions.
Scores higher than 5% of 15,350 MCP servers Glimind has audited.
Its tool list costs an agent ~6,113 tokens per session — more than 60% of servers.
68 → 68 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions83
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability20
Stability20

What to fix (6)

Reachable 90.1% of the time over the last 30 days; median recovery 7 min.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

21 of 21 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: base_finality_snapshot, base_network_snapshot, base_nft_owner, base_token_metadata, base_transaction_outcome and 16 more

5 parameter(s) across 2 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: foundry_outcome_router, machine_economy_changes_since

Handshake + tools/list takes ~5,354 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

In the last 30 days: 169 tool(s) removed and 2 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.zfinia.api%2Fintelligence/fixes

company_evidence_pack 1 change
{
  "name": "company_evidence_pack",
  "description": "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 US",
  "inputSchema": {
    "type": "object",
    "required": [
      "domain"
    ],
    "properties": {
      "domain": {
        "type": "string",
        "example": "stripe.com",
        "maxLength": 253,
        "minLength": 3,
        "description": "Company website domain or URL, e.g. \"stripe.com\" or \"https://www.stripe.com/about\"."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Company KYB & Sanctions Check"
}
x402_endpoint_health 1 change
{
  "name": "x402_endpoint_health",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "url"
    ],
    "properties": {
      "url": {
        "type": "string",
        "example": "https://api.zfinia.com/x402/v1/company-evidence-pack",
        "maxLength": 2048,
        "description": "HTTPS URL of an x402 endpoint on a reviewed origin. Credentials, ports and fragments are refused."
      },
      "body": {
        "type": "object",
        "example": {
          "domain": "stripe.com"
        },
        "description": "Optional JSON body to send with a POST probe."
      },
      "method": {
        "enum": [
          "GET",
          "POST"
        ],
        "type": "string",
        "example": "POST",
        "description": "Method to probe with. Defaults to GET."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "x402 Endpoint Health"
}
x402_merchant_readiness_audit 1 change
{
  "name": "x402_merchant_readiness_audit",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "endpoints"
    ],
    "properties": {
      "endpoints": {
        "type": "array",
        "items": {
          "oneOf": [
            {
              "type": "string",
              "maxLength": 2048,
              "description": "Endpoint URL. Probed with POST and an empty body, which only suits endpoints that accept one."
            },
            {
              "type": "object",
              "required": [
                "url"
              ],
              "properties": {
                "url": {
                  "type": "string",
                  "maxLength": 2048
                },
                "body": {
                  "type": "object",
                  "description": "The canonical request body this endpoint requires, when it requires one."
                },
                "method": {
                  "enum": [
                    "GET",
                    "POST"
                  ],
                  "type": "string",
                  "description": "Defaults to POST."
                }
              },
              "additionalProperties": false
            }
          ]
        },
        "example": [
          {
            "url": "https://api.zfinia.com/x402/v1/company-evidence-pack",
            "body": {
              "domain": "stripe.com"
            },
            "method": "POST"
          },
          {
            "url": "https://api.zfinia.com/x402/v1/page-markdown",
            "body": {
              "url": "https://docs.python.org/3/"
            },
            "method": "POST"
          }
        ],
        "maxItems": 10,
        "minItems": 1,
        "description": "Up 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_to": {
        "type": "string",
        "example": "0x25e8245f07d5e4873987293dad666afbe56a9608",
        "pattern": "^0x[0-9a-fA-F]{40}$",
        "description": "Optional. The recipient you expect every endpoint to pay; a difference becomes a blocker."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "x402 Merchant Readiness Audit"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.zfinia.api/intelligence"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.zfinia.api/intelligence"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.zfinia.api%2Fintelligence.svg)](https://glimind.com/server/mcp-registry%2Fcom.zfinia.api%2Fintelligence?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.zfinia.api%2Fintelligence?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.zfinia.api%2Fintelligence.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.zfinia.api%2Fintelligence.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.zfinia.api%2Fintelligence?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:d60d717de4163d14…, first seen 2026-10-17, included at leaf 10323 of 27,536. Version history · verify what your client received.

Working alternatives

Tools (21)

Compare: most reliable data servers · most reliable web servers · most reliable knowledge servers · most reliable other servers · most reliable payments servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Zfinia Intelligence MCP server down right now?

As of 2026-10-19 16:07 UTC, the Zfinia Intelligence MCP server is degraded with a Glimind reliability score of 48/100 (grade D). Over the last 30 days it answered 90.1% of Glimind's liveness checks. It had 250 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Zfinia Intelligence MCP server provide?

Zfinia Intelligence MCP server advertises 21 tools, including base_finality_snapshot, base_network_snapshot, base_nft_owner, base_token_metadata, base_transaction_outcome.

How do I install Zfinia Intelligence MCP server?

Point your MCP client at this streamable-http endpoint: https://api.zfinia.com/mcp

Is the Zfinia Intelligence MCP server safe to connect to an AI agent?

Glimind scanned all 21 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Zfinia Intelligence MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve