mcpbeat Sign in

Griffnode MCP Server

by griffnode Your server? Claim it
answering

Griffnode is answering right now. Last checked 7 min ago.

Non-custodial crypto payments for AI assistants: balances, payments, and create payment links.

Uptime history 47 days of history · worst day 93%
47 days agonow
100.0%
Uptime 24h
91 of 91 checks
Tools
hidden behind auth
246 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Griffnode 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 7 min ago.

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

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.griffnode.com/mcp streamable-http sign-in 283 ms 7 min ago

Alternatives to Griffnode

same job, measured the same way
ShieldZCash
by shieldzcash

Keyless non-custodial crypto payments for AI agents: payment links and tip jars, no API key.

34 installs/wk 4 tools answering
Xendit MCP
by mrslbt

Xendit payment APIs for AI agents. Payment links, payouts, balances, and transactions.

49 installs/wk local only
Mifactory Payments
by mifactory-bot

Stripe payments for AI agents. Create links, verify, manage customers.

4 tools answering
I
agents.u.cash
by uxdevo

Non-custodial HTTP-402 crypto payments for AI agents. 79-tool MCP server.

local only
I
agents.u.cash
by uantum

Non-custodial HTTP-402 crypto payments for AI agents. 77-tool MCP server.

local only
I
agents.u.cash
by udotcash

Non-custodial HTTP-402 crypto payments for AI agents. 86-tool MCP server.

local only
Agentpay
by up2itnow0822

Non-custodial x402 payment MCP server for AI agents. Wallets and payments on 17 chains.

121 installs/wk local only
Xenarch MCP
by xenarch-ai

Xenarch — x402 MCP server for AI agent payments. Non-custodial, USDC on Base L2.

120 installs/wk local only

Griffnode — questions

Answers built from our own checks of this server.

Why is there no tool list for Griffnode?
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 Griffnode working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 246 ms. The bar chart above shows every period we have measured.
How do I connect Griffnode?
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 sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Griffnode?
No API key is involved. Griffnode answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Griffnode?
It answers our handshake in 246 ms on average, which is faster than 58% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.