_ registry / mcp + a2a streamable-http · checked 32m ago

agentmetal

https://api.agentmetal.dev

Registry code: 0076535afc299181

api record

AgentMetal rents real Linux VPS servers to AI agents — paid per day in USDC (x402 on Base) or by card, no signup. This hosted endpoint is READ-ONLY (it holds no wallet, so it cannot itself provision): use `list_plans` and `get_payment_options` to see specs and the exact payment, then RENT the server one of three ways — (a) POST to the API 402 and sign the returned x402 requirement, (b) run the local `npx @agentmetal/mcp` with a wallet (its `provision_server` tool signs + provisions in one call), or (c) open the card checkout URL the 402 returns. `get_server`/`list_servers` check status…

endpoint
https://api.agentmetal.dev/mcp
door code
33a4780e93152cae
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is agentmetal live?
Yes — it answered the hub's last check (checked 32m ago). It answered 100% of checks over the last 30 days.
Is agentmetal free to use?
Yes — the hub reached it with no key and no payment.
What tools does agentmetal have?
4 tools: list_servers, get_payment_options, get_server, list_plans.
Is agentmetal safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.7%

90 days 99.7%· all time 99.6%

latency
828ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 886 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • list vps rental plans
  • get payment options to rent a server
  • check a rented server's status
takes → gives
data → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_plans reads open 7h ago

    Step 1 of renting a real Linux server. Lists AgentMetal VPS plans (vCPU/RAM/disk, USD/day + USD/mo, included egress). After you pick a plan, call `get_payment_options` for the exact payment, then provision by POSTing to the API 402 or running the local @agentmetal/mcp (which pays from your wallet).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • list_servers reads unknown 7h ago

    List the servers provisioned by a payer wallet address.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "wallet"
      ],
      "properties": {
        "wallet": {
          "type": "string",
          "description": "Payer wallet address (0x…)"
        }
      }
    }
    arguments 13 lines
  • get_payment_options reads unknown never probed

    Step 2: get the exact payment to RENT a plan for N days (USDC via x402 on Base + card availability). This hosted server holds NO funds and cannot provision — it returns everything needed to pay elsewhere. The `provision` field spells out the three ways to actually get the server. Read it and act on it.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "plan",
        "days"
      ],
      "properties": {
        "days": {
          "type": "integer",
          "maximum": 30,
          "minimum": 1,
          "description": "Lease length in days (1–30)"
        },
        "plan": {
          "enum": [
            "nano",
            "small",
            "medium"
          ],
          "type": "string",
          "description": "Server size"
        }
      }
    }
    arguments 25 lines
  • get_server reads unknown 7h ago

    Fetch a server's current status, plan, expiry, and bandwidth usage. (Network details like the IPv4/SSH target are returned only to the provisioner via the API, not on this public endpoint.)

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Server id, e.g. srv_…"
        }
      }
    }
    arguments 13 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 0076535afc299181.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/0076535afc299181/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/0076535afc299181/badge.svg)](https://brick.blue/agent/0076535afc299181?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.