KindleSMS - SMS Platform
Registry code: dca4a2a9e7350009
The Fastest Way to Reach Your Customers with SMS Launch campaigns in minutes, not days. Automate outreach, manage contacts, and convert more leads with our powerful SMS marketing platform.
from a public catalogue that lists it, not from the operator
- endpoint
- https://kindlesms.com/api/mcp
- protocol
- streamable-http ·2024-11-05
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is KindleSMS - SMS Platform live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is KindleSMS - SMS Platform free to use?
- Not measured yet.
- What tools does KindleSMS - SMS Platform have?
- 3 tools: list_sender_ids, send_sms, check_balance.
- Is KindleSMS - SMS Platform 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.
90 days 100%· all time 100%
last good check
of 3 tools
- degraded → live
- unknown → live
- topic
- communication sms & voice
- used for
- send an sms to a phone number
- check sms credit balance
- list approved sender ids
- takes → gives
- text → data
- tools
- 2 reads1 sends messages
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.
through this hub
successful
what callers paid
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.
list_sender_ids reads unknown never probed
List all approved and registered Sender IDs (brand names) on your KindleSMS account.
{ "type": "object", "properties": {} }arguments 4 linessend_sms sends messages unknown never probed
Send an SMS text message to a single recipient through KindleSMS. Costs 1 credit per standard message. If the user specifies a Sender ID (e.g. 'using Lesalb'), extract that name into 'sender_id' and remove that phrase from the 'message' body text.
{ "type": "object", "required": [ "to", "message" ], "properties": { "to": { "type": "string", "description": "The recipient's phone number with country code (e.g. '+233XXXXXXXXX' or '0XXXXXXXXX')." }, "message": { "type": "string", "description": "The clean text message body to send to the recipient." }, "sender_id": { "type": "string", "description": "Optional: The registered sender ID name (e.g. 'Lesalb', 'KindleSMS') to send from." } } }arguments 21 linescheck_balance reads unknown 19h ago
Check your current KindleSMS credit balance and see your registered approved Sender IDs.
{ "type": "object", "properties": {} }arguments 4 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's iddca4a2a9e7350009.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/dca4a2a9e7350009/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/dca4a2a9e7350009?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.