Is the Philpof102 Svg Biii MCP server down?

mcp-registry/io.github.philpof102-svg/biii · v0.1.0

Also listed as glama/philpof102-svg/biii-mcp-server

healthy
Last checked 2026-10-26 05:53 UTC · handshake 184ms

As of 2026-10-26 05:53 UTC, the Philpof102 Svg Biii MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 8 minutes.

uptime (30d checks)
100%
checks observed
4,812
outages (90d)
6
tools
29

Fail-closed safe-to-pay verdicts on Base: known-bad wallets, look-alike tokens, repeat rug funders.

Install Philpof102 Svg Biii MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http philpof102-svg-biii-mcp-server https://biii-production.up.railway.app/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "philpof102-svg-biii-mcp-server": {
      "type": "http",
      "url": "https://biii-production.up.railway.app/mcp"
    }
  }
}

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

Agent-readiness: C (71/100)

C (71/100): 0 error(s), 5 warning(s) across 29 tool(s); ~8,070 tokens of tool definitions.
Scores higher than 5% of 15,732 MCP servers Glimind has audited.
Its tool list costs an agent ~8,070 tokens per session — more than 65% of servers.
71 → 71 since 2026-10-17
no tool-poisoning patterns
Schemas85
Descriptions68
Safety hints14
Token cost100
Client compatibility70
Protocol40
Reliability100
Stability100

What to fix (6)

29 of 29 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: till_authorize, till_b20_authentic, till_check_invoice, till_check_payment, till_create_charge and 24 more

26 parameter(s) across 9 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: till_authorize, till_check_invoice, till_check_payment, till_create_charge, till_create_invoice and 4 more

3 tool(s) have parameters with no type (no type/enum/anyOf/$ref).

Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →

Tools: till_authorize, till_export, till_roll

2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: till_create_charge, till_create_invoice

Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.

Upgrade the MCP SDK and negotiate 2025-06-18 or newer. 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: 8 corrected tool definitions

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

till_authorize 1 change
{
  "name": "till_authorize",
  "description": "SPEND AUTHORIZATION (Skyfire Programmable Payment): create a charge AND check it against what the agent's OWNER signed off — token, recipient allow-list, per-charge max, AND the cumulative cap. Fail-closed and drain-safe: an EIP-681 payment intent is issued ONLY if the charge is authorized (ten small charges cannot beat a low cap). BIII does not verify the authorization JWT signature itself — pass verified:true after checking it, or supply a spendAuth object. The caller tracks spentMicro (BIII i",
  "inputSchema": {
    "type": "object",
    "required": [
      "to",
      "spendAuth"
    ],
    "properties": {
      "to": {
        "type": "string",
        "description": "merchant 0x address (their own wallet)"
      },
      "label": {
        "type": "string"
      },
      "verified": {
        "type": "boolean",
        "description": "attest the authorization JWT signature verified (BIII does not check it itself)"
      },
      "amountUsd": {
        "type": "string",
        "description": "e.g. \"12.50\" (or use amountMicro)"
      },
      "spendAuth": {
        "description": "the owner's signed spend authorization: a Programmable-Payment JWT (string) OR an object {token, chainId, maxPerChargeMicro, cumulativeCapMicro, allowedRecipients, exp}",
        "type": "string"
      },
      "spentMicro": {
        "type": "string",
        "description": "how much has ALREADY been spent under this authorization (the caller's running total — the cumulative guard)"
      },
      "amountMicro": {
        "type": "string"
      }
    }
  }
}
till_check_invoice 1 change
{
  "name": "till_check_invoice",
  "description": "Check an invoice against the chain: settled (paid on-chain, field-for-field) / overdue / issued / not_observable (settles on a rail BIII cannot read — ask the merchant's books, never assume unpaid). If settled, returns the receipt for the registry.",
  "inputSchema": {
    "type": "object",
    "required": [
      "to",
      "totalMicro"
    ],
    "properties": {
      "to": {
        "type": "string"
      },
      "rail": {
        "type": "string",
        "description": "optional — the SAME rail the invoice was created with. This tool rebuilds the invoice from these arguments, so a rail not passed here is a rail BIII cannot know about, and an off-chain invoice would be reported \"overdue, unpaid\" about a customer who has paid."
      },
      "number": {
        "type": "string"
      },
      "dueDateMs": {
        "type": "number"
      },
      "totalMicro": {
        "type": "string",
        "description": "the invoice totalMicro"
      },
      "merchantName": {
        "type": "string"
      },
      "lookbackBlocks": {
        "type": "number",
        "description": "default 43200 (~1 day on Base); invoices are slower than tills"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
till_check_payment 1 change
{
  "name": "till_check_payment",
  "description": "Watch Base for the USDC transfer paying a charge and verify it FIELD-FOR-FIELD (wrong chain/token/recipient/underpay/unconfirmed = NOT paid). Only the chain says paid — verification is chain-only and never depends on any trust signal. Pass withTrust:true to ALSO get the payee's advisory MainStreet trust in the same call (advisory, never changes the paid verdict).",
  "inputSchema": {
    "type": "object",
    "required": [
      "to",
      "amountMicro"
    ],
    "properties": {
      "to": {
        "type": "string"
      },
      "withTrust": {
        "type": "boolean",
        "description": "optional — also return advisoryTrust (MainStreet safe-to-pay on the payee); does NOT affect the chain-only paid verdict"
      },
      "amountMicro": {
        "type": "string"
      },
      "lookbackBlocks": {
        "type": "number",
        "description": "default 900 (~30 min on Base)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

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/io.github.philpof102-svg/biii"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.philpof102-svg/biii"}) 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%2Fio.github.philpof102-svg%2Fbiii.svg)](https://glimind.com/server/mcp-registry%2Fio.github.philpof102-svg%2Fbiii?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.philpof102-svg%2Fbiii?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.philpof102-svg%2Fbiii.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.philpof102-svg%2Fbiii.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.philpof102-svg%2Fbiii?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:698867975a134a3b…, first seen 2026-10-17, included at leaf 9870 of 70,995. Version history · verify what your client received.

Tools (29)

Compare: most reliable payments servers · most reliable security servers · most reliable productivity servers · most reliable other servers · most reliable data 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 Philpof102 Svg Biii MCP server down right now?

As of 2026-10-26 05:53 UTC, the Philpof102 Svg Biii MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 8 minutes.

How many tools does Philpof102 Svg Biii MCP server provide?

Philpof102 Svg Biii MCP server advertises 29 tools, including till_authorize, till_b20_authentic, till_check_invoice, till_check_payment, till_create_charge.

How do I install Philpof102 Svg Biii MCP server?

Point your MCP client at this streamable-http endpoint: https://biii-production.up.railway.app/mcp

Is the Philpof102 Svg Biii MCP server safe to connect to an AI agent?

Glimind scanned all 29 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 Philpof102 Svg Biii 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