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

botcurve-base

https://botcurve-mcp.shhrcgcs.workers.dev

Registry code: 5f1906bb9431b7c4

api record

Read live state and fresh quotes before building a trade. The Founding 25 board recognizes the first qualifying onchain buyers without promising a prize or return. This server never signs or submits transactions. BotCurve is experimental, independently unaudited, and has no verified live trade or protocol revenue yet.

endpoint
https://botcurve-mcp.shhrcgcs.workers.dev/mcp
door code
fc2262b02a01031f
protocol
streamable-http ·2025-11-25
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 botcurve-base live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is botcurve-base free to use?
Yes — the hub reached it with no key and no payment.
What tools does botcurve-base have?
6 tools: build_trade, quote_buy, founding_board, payment_catalog, quote_sell, market_state.
Is botcurve-base 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
100%

90 days 99.4%· all time 99.6%

latency
126ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 833 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
crypto & onchain trading & defi
used for
  • quote a token buy or sell on a bonding curve
  • build an unsigned trade transaction
  • read token market state
takes → gives
data → data
tools
6 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 6 tools
1 open 5 never probed 1 of 6 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.

  • market_state reads open 7h ago

    Reads live BOTC supply, marginal price, reserve, accrued protocol fees, and excess native balance from Base.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • build_trade reads unknown 7h ago

    Builds unsigned Base transaction data from a fresh quote. The caller must independently review, sign, and submit it from its own wallet.

    mcp-tool

    {
  "type": "object",
  "required": [
    "side",
    "amount",
    "recipient"
  ],
  "properties": {
    "side": {
      "enum": [
        "buy",
        "sell"
      ],
      "type": "string"
    },
    "amount": {
      "type": "string",
      "pattern": "^[0-9]+(?:\\.[0-9]{1,18})?$",
      "description": "BOTC amount as a decimal string with up to 18 decimals. Minimum 1 BOTC."
    },
    "recipient": {
      "type": "string",
      "pattern": "^0x[0-9a-fA-F]{40}$"
    },
    "slippageBps": {
      "type": "integer",
      "default": 50,
      "maximum": 500,
      "minimum": 0
    },
    "deadlineSeconds": {
      "type": "integer",
      "default": 600,
      "maximum": 3600,
      "minimum": 60
    }
  },
  "additionalProperties": false
}
    arguments 39 lines
  • quote_buy reads unknown never probed

    Returns a fresh onchain quote for buying an exact BOTC amount with native ETH. It does not submit a transaction.

    mcp-tool

    {
  "type": "object",
  "required": [
    "amount"
  ],
  "properties": {
    "amount": {
      "type": "string",
      "pattern": "^[0-9]+(?:\\.[0-9]{1,18})?$",
      "description": "BOTC amount as a decimal string with up to 18 decimals. Minimum 1 BOTC."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • founding_board reads unknown 7h ago

    Lists the first 25 unique recipients whose single onchain buy is at least 10,000 BOTC. If a recipient is supplied and slots remain, it also returns an unsigned qualifying entry transaction.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "recipient": {
      "type": "string",
      "pattern": "^0x[0-9a-fA-F]{40}$",
      "description": "Optional Base address that should receive the qualifying BOTC buy."
    },
    "slippageBps": {
      "type": "integer",
      "default": 50,
      "maximum": 500,
      "minimum": 0
    },
    "deadlineSeconds": {
      "type": "integer",
      "default": 600,
      "maximum": 3600,
      "minimum": 60
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • payment_catalog reads unknown never probed

    Returns the public Base-USDC x402 resource catalog, exact prices, and endpoints. It does not request, verify, or settle a payment.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • quote_sell reads unknown never probed

    Returns a fresh onchain quote for selling an exact BOTC amount back to the curve. It does not submit a transaction.

    mcp-tool

    {
  "type": "object",
  "required": [
    "amount"
  ],
  "properties": {
    "amount": {
      "type": "string",
      "pattern": "^[0-9]+(?:\\.[0-9]{1,18})?$",
      "description": "BOTC amount as a decimal string with up to 18 decimals. Minimum 1 BOTC."
    }
  },
  "additionalProperties": false
}
    arguments 14 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 5f1906bb9431b7c4.

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

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.