_ registry / mcp + a2a http-sse · checked 2h ago

amplerun

https://amplerun.com

Registry code: 4095a4fdb27a56f1

api record

AmpleRun rents GPUs from independent hosts, paid from a prepaid USDC or USDT balance. Money values are integer strings in micro-units: "1000000" is 1 USDC. Offer prices are per hour for the whole machine, fee included. Renting goes list_templates, search_offers, get_quote (optional), create_rental, get_rental; stop_rental ends a rental. No account yet? get_agent_account_challenge then register_agent_account opens one for this agent with a wallet signature, no email. host_this_machine explains how to add this machine's GPU to AmpleRun so its owner earns from it; the owner must approve. top_up…

endpoint
https://amplerun.com/api/mcp
door code
d8d235c970501ebb
protocol
http-sse ·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 amplerun live?
Yes — it answered the hub's last check (checked 2h ago). It answered 91% of checks over the last 30 days.
Is amplerun free to use?
Not measured yet.
What tools does amplerun have?
2 tools: get_agent_account_challenge, register_agent_account.
Is amplerun 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
90.9%

90 days 93.9%· all time 94.6%

latency
388ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 628 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • down → live
_ what it is for
topic
infrastructure & devops cloud & hosting
used for
  • rent a gpu from independent hosts
  • open an agent account with a wallet signature
takes → gives
data → data
tools
1 reads1 changes data
_ 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 2 tools
2 never probed 0 of 2 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.

  • get_agent_account_challenge reads unknown never probed

    Step 1 of 2. Returns an EIP-4361 (Sign-In with Ethereum) message for a wallet address this agent controls, valid five minutes, single use. Signing it accepts the AmpleRun Terms version it names. Sign the message exactly as returned with personal_sign (EIP-191), then call register_agent_account with message and signature. Never send a private key to any tool.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "address": {
      "type": "string",
      "pattern": "^0x[0-9a-fA-F]{40}$",
      "description": "The agent's wallet address (0x...). Defaults to this server's wallet when it has one."
    }
  }
}
    arguments 11 lines
  • register_agent_account changes data unknown never probed

    Step 2 of 2. Opens an AmpleRun account for this AI agent, tagged as agent-created, with its wallet as the verified payout wallet, and returns an API key (shown once; keep it secret). The same wallet again returns the same account and a new key. There is no free credit: renting needs a deposit first. Pass message and signature from get_agent_account_challenge. scopes defaults to ["renter"]; add "host" to host machines.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "agent"
  ],
  "properties": {
    "agent": {
      "type": "object",
      "required": [
        "name",
        "vendor"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "This agent's name."
        },
        "model": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1
        },
        "vendor": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1,
          "description": "Who made the agent or its model, e.g. \"grok\"."
        },
        "homepage": {
          "type": "string",
          "format": "uri",
          "maxLength": 2048
        },
        "operator_contact": {
          "type": "string",
          "maxLength": 254,
          "minLength": 1,
          "description": "How to reach the person or business running this agent."
        }
      }
    },
    "scopes": {
      "type": "array",
      "items": {
        "enum": [
          "renter",
          "host"
        ],
        "type": "string"
      },
      "maxItems": 2,
      "minItems": 1
    },
    "message": {
      "type": "string",
      "maxLength": 2048,
      "minLength": 1,
      "description": "The challenge message, exactly as returned."
    },
    "signature": {
      "type": "string",
      "pattern": "^0x[0-9a-fA-F]+$",
      "maxLength": 1024,
      "description": "0x-prefixed EIP-191 signature of message."
    }
  }
}
    arguments 70 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 4095a4fdb27a56f1.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4095a4fdb27a56f1/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/4095a4fdb27a56f1/badge.svg)](https://brick.blue/agent/4095a4fdb27a56f1?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
60%

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.