Skip to content
FOXIFY logo

FOXIFY MCP server

Which MCP servers are FOXIFY's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to FOXIFY

Whose server it is
  • Registry namepro.foxify/agent-commerceverified in the MCP registry

The registry name sits under foxify.pro. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools3
  • Server calls itselfFOXIFY Agent Commerce
  • Server version0.2.1
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 909 ms.

Should an agent connect itNot proven either way yet
  • Its tools do preflight x402 payment intents before an agent pays, but not map which tools and credentials a public repository exposes.
  • Checked on 2 of the 7 days it takes to judge reliability.

Once connected

  • For "preflight x402 payment intents before an agent pays", the likely first call is verify_agent_payment_intent.
  • Parameters are untyped or undescribed in 2 of 3 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 2, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • What an agent can do with it1 of 2 use cases
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer1072 ms
  • Space in an agent's context≈ 1,183 tokensthe definitions of all its tools (3), which an agent carries on every turn
  • Tool definitionsB · 89 of 100
  • Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 2 of 3

What an agent can do with it

  • cannot · map which tools and credentials a public repository exposes
  • can do · preflight x402 payment intents before an agent pays
  • not sure · verify action outcomes by reading back provider state

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers3 tools · read 2026-10-26
  • foxify_preflight_info

    Free metadata for FOXIFY machine-payable authority preflight tools.

  • verify_agent_payment_intent

    Paid transaction preflight. Checks mandate, amount, destination, merchant, expiry and replay risk before an autonomous payment executes. Costs $0.05 USDC on Base.

  • verify_agent_action_intent

    Paid exact-action authority preflight for consequential agent tool calls. Binds subject, tool, operation, target, canonical parameters, authority lifetime, retries and postcondition requirements. Costs $0.25 USDC on Base.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "agent-commerce": {
      "type": "http",
      "url": "https://foxify.pro/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http foxify https://foxify.pro/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://foxify.pro/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.