Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

CurveCall

REMOTE · CURVECALL.ONRENDER.COM

Paid token market data, risk signals and trade simulations for AI agents. USDC via x402.

+3 this week 76 Trust /100

Last scanned (17 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Recent critical change

Authorization (19 Nov 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2342 tokens (~212/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Nov 26 +3
    • Authorization: unverified → fail ▼ critical
    • Tool “bundle_check” is now declared destructive security
    • Tool “contract_check” is now declared destructive security
    • Tool “deployer_history” is now declared destructive security
    • Tool “precheck” is now declared destructive security
    • Tool “quote_buy” is now declared destructive security
    • Tool “quote_sell” is now declared destructive security
    • Tool “search_tokens” is now declared destructive security
    • Tool “token_risk” is now declared destructive security
    • Tool “token_snapshot” is now declared destructive security
    • Tool “verdict” is now declared destructive security
    • Tool “wallet_snapshot” is now declared destructive security
    • Schema quality: pass → fail ▼ functional
    • Tool coverage: 0% → 100% ▲ functional
    • Schema quality: fair → good functional
    • “bundle_check” reworded the description of “address” cosmetic
    • “bundle_check” reworded the description of “chain” cosmetic
    • “bundle_check” reworded the description of “payment” cosmetic
    • “contract_check” reworded the description of “address” cosmetic
    • “contract_check” reworded the description of “chain” cosmetic
    • “contract_check” reworded the description of “payment” cosmetic
    • “deployer_history” reworded the description of “address” cosmetic
    • “deployer_history” reworded the description of “chain” cosmetic
    • “deployer_history” reworded the description of “payment” cosmetic
    • “precheck” reworded the description of “address” cosmetic
    • “precheck” reworded the description of “amount_in” cosmetic
    • “precheck” reworded the description of “chain” cosmetic
    • “precheck” reworded the description of “fee_bps” cosmetic
    • “precheck” reworded the description of “payment” cosmetic
    • “precheck” reworded the description of “side” cosmetic
    • “quote_buy” reworded the description of “amount_in” cosmetic
    • “quote_buy” reworded the description of “fee_bps” cosmetic
    • “quote_buy” reworded the description of “payment” cosmetic
    • “quote_buy” reworded the description of “quote_reserves” cosmetic
    • “quote_buy” reworded the description of “token_reserves” cosmetic
    • “quote_sell” reworded the description of “amount_in” cosmetic
    • “quote_sell” reworded the description of “fee_bps” cosmetic
    • “quote_sell” reworded the description of “payment” cosmetic
    • “quote_sell” reworded the description of “quote_reserves” cosmetic
    • “quote_sell” reworded the description of “token_reserves” cosmetic
    • “search_tokens” reworded the description of “chain” cosmetic
    • “search_tokens” reworded the description of “limit” cosmetic
    • “search_tokens” reworded the description of “payment” cosmetic
    • “search_tokens” reworded the description of “q” cosmetic
    • “token_risk” reworded the description of “address” cosmetic
    • “token_risk” reworded the description of “chain” cosmetic
    • “token_risk” reworded the description of “payment” cosmetic
    • “token_snapshot” reworded the description of “address” cosmetic
    • “token_snapshot” reworded the description of “chain” cosmetic
    • “token_snapshot” reworded the description of “payment” cosmetic
    • “verdict” reworded the description of “address” cosmetic
    • “verdict” reworded the description of “amount_usd” cosmetic
    • “verdict” reworded the description of “chain” cosmetic
    • “verdict” reworded the description of “payment” cosmetic
    • “wallet_snapshot” reworded the description of “address” cosmetic
    • “wallet_snapshot” reworded the description of “chain” cosmetic
    • “wallet_snapshot” reworded the description of “payment” cosmetic
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
    • Tool “bundle_check” rewrote its description, which is the text the model reads security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Oct 26 0
    • Stability: 0.97 → pass security
  • 23 Oct 26 73
    • The server rewrote its instructions, which are the text every model session reads security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://curvecall.onrender.com/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=onrender.com CN=WE1,O=Google Trust Services,C=US 19 Nov 2026 17 Feb 2027 ECDSA 256 ECDSA-SHA256 8d72a13c2c41648513b9d014eb5e0339
SANs: onrender.com, *.onrender.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of curvecall.onrender.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
onrender.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://curvecall.onrender.com/mcp/ Verified 200
http (plaintext) http://curvecall.onrender.com/mcp/ HTTPS enforced 301 https://curvecall.onrender.com/mcp/
MCP tools · 11 exposed · ~2,203 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
bundle_check ~235

Bundle/sniper signals for a token (base, bsc, robinhood, arc): who bought in the first blocks after launch, how much of the early supply they took, and whether any were funded by the deployer or a shared wallet. Signals, not advice. Elysium returns verified holder concentration and transfer clustering only, not verified buys or insider attribution. $0.02 USDC. Data by GeckoTerminal; Elysium uses its public RPC.

NameTypeReqDescription
addressstringyesPublic token contract address on the selected chain. EVM addresses use 0x plus 40 hexadecimal characters; Solana uses its base58 mint address.
chainstringyesSupported chain: base, bsc, robinhood, arc or elysium. Elysium returns holder concentration and transfer clustering, not verified purchases or insider attribution.
payment––Optional base64-encoded x402 payment payload returned by an authorized payment client, not a private key or API token. Omit to receive payment requirements. A successful authorized call may settle a…

Structured output declared, but exposes no named fields.

No examples provided.

contract_check ~179

On-chain contract check (EVM chains: base, ethereum, arbitrum, optimism, polygon, bsc): ownership renounced?, LP burn share, ERC-20 metadata, red flags. $0.01 USDC.

NameTypeReqDescription
addressstringyesPublic token contract address on the selected chain. EVM addresses use 0x plus 40 hexadecimal characters; Solana uses its base58 mint address.
chainstringyesSupported EVM chain identifier such as base, ethereum, arbitrum, optimism, polygon or bsc; support depends on configured RPC providers.
payment––Optional base64-encoded x402 payment payload returned by an authorized payment client, not a private key or API token. Omit to receive payment requirements. A successful authorized call may settle a…

Structured output declared, but exposes no named fields.

No examples provided.

deployer_history ~216

Deployer launch history from CurveCall's hourly launch-outcome index on Base, Robinhood Chain and Arc (built since 2026-09-24): every launch this deployer made and how it ended (survived, rugged, died), with rug rate and dev-behavior flags (dev moved tokens, relaunch count). Answers 'has this deployer rugged before?' $0.01 USDC. Data by GeckoTerminal.

NameTypeReqDescription
addressstringyesPublic deployer wallet address, 0x plus 40 hexadecimal characters, whose indexed launch history is requested.
chainstringyesIndexed chain: base, robinhood or arc. History begins September 24, 2026 and is not complete chain history.
payment––Optional base64-encoded x402 payment payload returned by an authorized payment client, not a private key or API token. Omit to receive payment requirements. A successful authorized call may settle a…

Structured output declared, but exposes no named fields.

No examples provided.

precheck ~295

Pre-trade bundle: snapshot + risk screen + curve trade simulation in ONE call. Tells you what your buy will do - quote, slippage, rug-risk verdict. $0.01 USDC. No other x402 service sells trade simulation.

NameTypeReqDescription
addressstringyesPublic token contract address on the selected chain. EVM addresses use 0x plus 40 hexadecimal characters; Solana uses its base58 mint address.
amount_in––Optional positive simulated trade input: quote-asset units for buy, token units for sell. Omit to skip simulation. No trade is executed.
chainstringyesLowercase chain identifier used by the data provider, for example base, ethereum or solana. Coverage varies by tool and upstream data availability.
fee_bpsnumber–Simulated trading fee in basis points; 100 means 1 percent. Curve simulation requires at least 0 and less than 10000. This is not the CurveCall API charge.
payment––Optional base64-encoded x402 payment payload returned by an authorized payment client, not a private key or API token. Omit to receive payment requirements. A successful authorized call may settle a…
sidestring–Simulation direction: buy spends quote asset to receive tokens; sell spends tokens to receive quote asset. Must be buy or sell.

Structured output declared, but exposes no named fields.

No examples provided.

quote_buy ~218

Bonding-curve BUY quote (constant product, virtual reserves). $0.001 USDC.

NameTypeReqDescription
amount_innumberyesPositive amount of quote asset to spend in the simulation, in the same units as quote_reserves. No trade is executed.
fee_bpsnumber–Simulated trading fee in basis points; 100 means 1 percent. Curve simulation requires at least 0 and less than 10000. This is not the CurveCall API charge.
payment––Optional base64-encoded x402 payment payload returned by an authorized payment client, not a private key or API token. Omit to receive payment requirements. A successful authorized call may settle a…
quote_reservesnumberyesPositive virtual reserve amount of the quote asset in consistent human-readable asset units, not USD unless the quote asset is USD-denominated.
token_reservesnumberyesPositive virtual token reserve amount in human-readable token units, consistent with the amount supplied.

Structured output declared, but exposes no named fields.

No examples provided.

quote_sell ~216

Bonding-curve SELL quote (constant product, virtual reserves). $0.001 USDC.

NameTypeReqDescription
amount_innumberyesPositive token amount to sell in the simulation, in the same units as token_reserves. No trade is executed.
fee_bpsnumber–Simulated trading fee in basis points; 100 means 1 percent. Curve simulation requires at least 0 and less than 10000. This is not the CurveCall API charge.
payment––Optional base64-encoded x402 payment payload returned by an authorized payment client, not a private key or API token. Omit to receive payment requirements. A successful authorized call may settle a…
quote_reservesnumberyesPositive virtual reserve amount of the quote asset in consistent human-readable asset units, not USD unless the quote asset is USD-denominated.
token_reservesnumberyesPositive virtual token reserve amount in human-readable token units, consistent with the amount supplied.

Structured output declared, but exposes no named fields.

No examples provided.

search_tokens ~149

Search tokens by name, symbol or contract address across chains. $0.005 USDC.

NameTypeReqDescription
chain––Optional lowercase chain identifier to filter results, for example base or solana. Omit to search across chains.
limitinteger–Maximum number of search results, from 1 to 25; default 10.
payment––Optional base64-encoded x402 payment payload returned by an authorized payment client, not a private key or API token. Omit to receive payment requirements. A successful authorized call may settle a…
qstringyesNon-empty token name, symbol or public contract address to search for.

Structured output declared, but exposes no named fields.

No examples provided.

token_risk ~154

Heuristic 0-100 token risk screen with explainable flags. $0.01 USDC.

NameTypeReqDescription
addressstringyesPublic token contract address on the selected chain. EVM addresses use 0x plus 40 hexadecimal characters; Solana uses its base58 mint address.
chainstringyesLowercase chain identifier used by the data provider, for example base, ethereum or solana. Coverage varies by tool and upstream data availability.
payment––Optional base64-encoded x402 payment payload returned by an authorized payment client, not a private key or API token. Omit to receive payment requirements. A successful authorized call may settle a…

Structured output declared, but exposes no named fields.

No examples provided.

token_snapshot ~156

Normalized token market snapshot (price, liquidity, FDV, volume, age). $0.005 USDC.

NameTypeReqDescription
addressstringyesPublic token contract address on the selected chain. EVM addresses use 0x plus 40 hexadecimal characters; Solana uses its base58 mint address.
chainstringyesLowercase chain identifier used by the data provider, for example base, ethereum or solana. Coverage varies by tool and upstream data availability.
payment––Optional base64-encoded x402 payment payload returned by an authorized payment client, not a private key or API token. Omit to receive payment requirements. A successful authorized call may settle a…

Structured output declared, but exposes no named fields.

No examples provided.

verdict ~227

START HERE before buying a token. One call returns a buy / watch / avoid decision with the reasons, risk score, key numbers (price, liquidity, volume, age) and heuristic sizing and stop distance. $0.01 USDC. For full raw data use precheck. Heuristic screen, not financial advice.

NameTypeReqDescription
addressstringyesPublic token contract address on the selected chain. EVM addresses use 0x plus 40 hexadecimal characters; Solana uses its base58 mint address.
amount_usd––Optional positive USD trade budget used only for heuristic sizing, not for executing a trade or authorizing the API payment.
chainstringyesLowercase chain identifier used by the data provider, for example base, ethereum or solana. Coverage varies by tool and upstream data availability.
payment––Optional base64-encoded x402 payment payload returned by an authorized payment client, not a private key or API token. Omit to receive payment requirements. A successful authorized call may settle a…

Structured output declared, but exposes no named fields.

No examples provided.

wallet_snapshot ~158

On-chain wallet snapshot (EVM chains): contract or EOA, tx count, native balance, fresh-wallet flag. $0.005 USDC.

NameTypeReqDescription
addressstringyesPublic EVM wallet or contract address, 0x plus 40 hexadecimal characters; never a seed phrase or private key.
chainstringyesSupported EVM chain identifier such as base, ethereum, arbitrum, optimism, polygon or bsc; support depends on configured RPC providers.
payment––Optional base64-encoded x402 payment payload returned by an authorized payment client, not a private key or API token. Omit to receive payment requirements. A successful authorized call may settle a…

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the CurveCall MCP server?

CurveCall is a hosted endpoint at https://curvecall.onrender.com/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · curvecall.onrender.com

# add to Claude Code
claude mcp add --transport http arbonomous-curvecall 'https://curvecall.onrender.com/mcp/'
Common questions

What is the CurveCall MCP server?

CurveCall is an MCP server listed in the public MCP registry as io.github.arbonomous/curvecall. Paid token market data, risk signals and trade simulations for AI agents. USDC via x402. This page covers its hosted endpoint (https://curvecall.onrender.com/mcp/).

Is the CurveCall MCP server safe to use?

CurveCall scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the CurveCall MCP server expose?

CurveCall exposes 11 tools: quote_buy, quote_sell, token_snapshot, token_risk, verdict, and 6 more. Their descriptions and schemas cost roughly 2,203 tokens of context every time the server is loaded.

Does the CurveCall MCP server require authentication?

No. We connected to CurveCall without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the CurveCall MCP server still maintained?

CurveCall is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the CurveCall MCP server?

VerifyMCP ran 13 checks on CurveCall, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.