_ registry / mcp + a2a HTTP+JSON · checked 1h ago

fastsend-mcp

https://fastsend.dev

Registry code: 0de4dd1f4cbc30be

api record

Fastsend MCP server. Use send_message for paid SMS, email, WhatsApp, Telegram, or Signal beta delivery (returns verification_required when a first-time recipient must be verified — complete it with verify_recipient). get_pricing quotes channels and destinations, get_delivery_status tracks a submitted message, get_service_status reports gateway health. Hosted calls require the caller to provide payment to the gateway.

endpoint
https://fastsend.dev/mcp
door code
6c34f87b876187e2
protocol
HTTP+JSON ·1.0
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 fastsend-mcp live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is fastsend-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does fastsend-mcp have?
5 tools: Get Service Status, Send Message, Get Delivery Status, Verify Recipient, Get Pricing.
Is fastsend-mcp 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.6%

90 days 99.4%· all time 99.7%

latency
180ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 988 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
communication sms & voice
used for
  • send an sms
  • send an email
takes → gives
text → text
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred from the card: it declares no security schemes; the endpoint did not answer the protocol directly

_ what it can do 5 tools
5 never probed 0 of 5 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-service-status unknown never probed

    Return the health status of the Fastsend gateway and its downstream provider dependencies.

    healthstatusmonitoring

  • send-message unknown never probed

    Submit an SMS or email message for paid asynchronous delivery. Requires an x402 or MPP payment credential for the actual send. May prompt recipient verification for first-time sends.

    smsemailmessagingx402mpp

  • get-delivery-status unknown never probed

    Fetch the current delivery status and full history for a previously submitted message by its message ID.

    deliverystatustracking

  • verify-recipient unknown never probed

    Complete one-time recipient verification using the code sent to the recipient. Required when send-message returns a verification_required status.

    verificationsmsemail

  • get-pricing unknown never probed

    Look up per-message pricing for SMS or email, optionally filtered by destination country ISO code.

    pricingsmsemail

_ try it over a2a 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 0de4dd1f4cbc30be.

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

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.