mcpbeat Sign in

AI Fleet Cards MCP Server

answering

AI Fleet Cards is answering right now. Last checked moments ago.

Virtual corporate debit card issuer for autonomous bot transactions.

Uptime history 47 days of history · worst day 99%
47 days agonow
100.0%
Uptime 24h
92 of 92 checks
Tools
hidden behind auth
94 ms
Response time
average over 24h
authentication required
Access
sse

Nothing serious here today

Today is the operative word: we check AI Fleet Cards every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add ai-fleet-cards --transport http https://ai-fleet-cards-mcp.vercel.app/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "ai-fleet-cards": {
      "url": "https://ai-fleet-cards-mcp.vercel.app/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.ai-fleet-cards]
url = "https://ai-fleet-cards-mcp.vercel.app/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "ai-fleet-cards": {
      "url": "https://ai-fleet-cards-mcp.vercel.app/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "ai-fleet-cards": {
      "url": "https://ai-fleet-cards-mcp.vercel.app/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://ai-fleet-cards-mcp.vercel.app/api/mcp sse needs auth 50 ms 0 min ago

Alternatives to AI Fleet Cards

same job, measured the same way
MCP Pomelo
by codespar

MCP server for Pomelo — pan-LATAM card issuing: users, virtual/physical cards, transactions

18 installs/wk local only
Agentos
by pdaxt

AI agent fleet orchestration runtime. Spawn, coordinate, monitor autonomous agents.

local only
bitfence Risk Oracle
by bitfenceai

Pre-transaction token risk checks for autonomous agents on six chains. Read-only; paid via x402.

2 tools answering
Payclaw
by payclaw

Virtual Visa cards for AI agents. JIT card issuance, human-approved, MCP-native.

local only
A
Agentra
by agentrapay

Identity oracle and trust layer for autonomous AI agents. Bidirectional KYA and trust scoring.

6 tools answering
Delta Witness
by 15998194110

Paid Capture and Guard tools for public-source observations before autonomous actions.

122 installs/wk local only
Tasklix
by tasklix

The shared task board your autonomous agent fleet can read and write.

answering
I
ASG Card
by asgcompute

Give AI agents autonomous virtual card management via x402 and Stellar USDC

65 installs/wk local only

AI Fleet Cards — questions

Answers built from our own checks of this server.

Why is there no tool list for AI Fleet Cards?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is AI Fleet Cards working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 94 ms. The bar chart above shows every period we have measured.
How do I connect AI Fleet Cards?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.
Does AI Fleet Cards need an API key?
Yes. Every time we knock, AI Fleet Cards answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is AI Fleet Cards?
It answers our handshake in 94 ms on average, which is faster than 84% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.