Paid2Call
REMOTE · API.PAID2CALL.COM
Launch pump.fun tokens whose fees pay callers in USDC. Find paying pools, register calls, claim.
Available components
Last scanned (5 hours ago)
Scores higher than 7% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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 Security49
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 530, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 530. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 4 Oct 26 20
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 3 Oct 26 0
- Tool “create_launch_draft” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 2 Oct 26 0
First indexed and scored.
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 5 Nov 2026 · Probed https://api.paid2call.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=paid2call.com | CN=YE1,O=Let's Encrypt,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5f2f92043496292cbcc8914a67611e8cd94 |
| SANs: *.paid2call.com, paid2call.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.paid2call.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| paid2call.com. | present | 2371 | 13 | Verified |
| api.paid2call.com. | Verified address RRset verified with the apex keys |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 530 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.paid2call.com/mcp | HTTP error | 530 | |
| http (plaintext) | http://api.paid2call.com/mcp | Inconclusive | 530 |
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 →
create_launch_draft ~265
Prepare a token launch. Nothing is created on-chain. reward_levels: e.g. [{"followers": 100, "reward_usdc": 10}, {"followers": 1000, "reward_usdc": 40}]. image_base64: the token image itself (PNG, JPEG, WEBP or GIF, square, 1 MB max). Paid2Call never downloads images from a URL; image_url is refused. Returns signing_url for a human (they review and sign on paid2call.com) and draft_id for an agent with its own wallet (see prepare_launch_transactions). The draft expires after 24 hours.
| Name | Type | Req | Description |
|---|---|---|---|
| bonus_every | string | – | – |
| callers_share_pct | number | – | – |
| description | string | – | – |
| first_buy_sol | number | – | – |
| fomo_bonus | boolean | – | – |
| hold_minutes | integer | – | – |
| image_base64 | string | – | – |
| image_url | string | – | – |
| minimum_position_usd | number | – | – |
| name | string | yes | – |
| reward_levels | array | yes | – |
| symbol | string | yes | – |
| telegram | string | – | – |
| string | – | – | |
| website | string | – | – |
No output schema declared.
No examples provided.
find_my_callouts ~71
The wallet's pump.fun callouts for this token that Paid2Call can see (max 20). Each callout_id can be registered with register_for_payment. Only callouts that mention paid2call.com are paid.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | – |
| wallet | string | yes | – |
No output schema declared.
No examples provided.
find_paying_pools ~102
Tokens whose callout pool is open, with what one call pays by follower count. sort: balance (most USDC first), new, volume, mcap, paid. A paid callout = buy the minimum, post the call on pump.fun mentioning paid2call.com, hold for the hold time, then register_for_payment.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| search | string | – | – |
| sort | string | – | – |
No output schema declared.
No examples provided.
get_caller_balance ~38
What the platform owes this caller, per token, in USDC, and what can be claimed now.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | – |
No output schema declared.
No examples provided.
get_fomo_bonus ~71
The +20% FOMO bonus for this token: the wallet's personal code to put in a FOMO thesis with paid2call.com, the theses seen, and the bonus amount. Only after a confirmed pump.fun reward.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | – |
| wallet | string | yes | – |
No output schema declared.
No examples provided.
get_launch_options ~28
What a Paid2Call launch can be set to, and whether launches are open right now.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_launch_status ~38
After a launch: is the token on-chain and listed on Paid2Call, and where to see it.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | – |
No output schema declared.
No examples provided.
get_pool ~36
One token's callout pool: rewards, rules, balance, recent payments and whether registration is open.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | – |
No output schema declared.
No examples provided.
get_signing_message ~153
The exact text a wallet must sign (signMessage, UTF-8, base58 signature) before an action. action: "launch" (prove you hold the creator wallet; valid 10 minutes), "queue" (register a callout for payment; needs mint and callout_id), "fomo_bonus" (claim the +20% FOMO bonus; needs mint and event_id). For queue and fomo_bonus, pass the returned issued_at unchanged; it is valid 15 minutes.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| callout_id | string | – | – |
| event_id | string | – | – |
| mint | string | – | – |
| wallet | string | yes | – |
No output schema declared.
No examples provided.
prepare_claim_transaction ~85
For a caller agent with its own wallet: the claim transaction for one token's balance. Sign it with the wallet, send it to Solana yourself (the wallet pays a tiny network fee), then call report_claim_sent. A human can claim instead at https://paid2call.com/claims.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | – |
| wallet | string | yes | – |
No output schema declared.
No examples provided.
prepare_launch_transactions ~119
For an agent that holds its own Solana wallet: build the launch transactions from a draft. challenge/signature: from get_signing_message(action="launch") signed by wallet. Returns transactions to sign with that wallet (base64, unsigned by you) and submit IN ORDER with submit_signed_transaction, waiting for each to confirm. The wallet pays the network fees and the first buy.
| Name | Type | Req | Description |
|---|---|---|---|
| challenge | string | yes | – |
| draft_id | string | yes | – |
| signature | string | yes | – |
| wallet | string | yes | – |
No output schema declared.
No examples provided.
quote_first_buy ~49
How much of the supply a creator's first buy gets (PUMP pair, 3% fee). Give sol or percent_of_supply.
| Name | Type | Req | Description |
|---|---|---|---|
| percent_of_supply | – | – | – |
| sol | – | – | – |
No output schema declared.
No examples provided.
register_fomo_bonus ~75
Link a FOMO thesis to the wallet for the +20% bonus. Sign get_signing_message(action="fomo_bonus") first.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | – |
| issued_at | integer | yes | – |
| mint | string | yes | – |
| signature | string | yes | – |
| wallet | string | yes | – |
No output schema declared.
No examples provided.
register_for_payment ~89
Register a callout to be paid from the token's pool. Sign get_signing_message(action="queue") first. Payment is made by the platform once purchase, call, followers and hold are verified.
| Name | Type | Req | Description |
|---|---|---|---|
| callout_id | string | yes | – |
| issued_at | integer | yes | – |
| mint | string | yes | – |
| signature | string | yes | – |
| wallet | string | yes | – |
No output schema declared.
No examples provided.
report_claim_sent ~55
Tell Paid2Call a claim transaction was sent, so the balance shows it as paying.
| Name | Type | Req | Description |
|---|---|---|---|
| days | string | yes | – |
| mint | string | yes | – |
| signature | string | yes | – |
| wallet | string | yes | – |
No output schema declared.
No examples provided.
submit_signed_transaction ~79
Relay a launch transaction you signed. Only transactions prepared by Paid2Call in the last 3 minutes are accepted; the server adds the token address signature. Waits up to 60 seconds for confirmation by default.
| Name | Type | Req | Description |
|---|---|---|---|
| last_valid_block_height | – | – | – |
| transaction_base64 | string | yes | – |
| wait_for_confirmation | boolean | – | – |
No output schema declared.
No examples provided.
How do I install the Paid2Call MCP server?
Paid2Call is a hosted endpoint at https://api.paid2call.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 · api.paid2call.com
claude mcp add --transport http com-paid2call-paid2call 'https://api.paid2call.com/mcp'
What is the Paid2Call MCP server?
Paid2Call is an MCP server listed in the public MCP registry as com.paid2call/paid2call. Launch pump.fun tokens whose fees pay callers in USDC. Find paying pools, register calls, claim. This page covers its hosted endpoint (https://api.paid2call.com/mcp).
Is the Paid2Call MCP server safe to use?
Paid2Call scores 20 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 Paid2Call MCP server expose?
Paid2Call exposes 16 tools: get_launch_options, quote_first_buy, create_launch_draft, get_signing_message, prepare_launch_transactions, and 11 more. Their descriptions and schemas cost roughly 1,353 tokens of context every time the server is loaded.
Does the Paid2Call MCP server require authentication?
Its publisher declares no required credentials for Paid2Call. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Paid2Call MCP server still maintained?
Paid2Call is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.