
sms-florin MCP server
Which MCP servers are sms-florin's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-27
- Registry namecom.flo-voice1/acp-sandboxverified in the MCP registry
The registry name sits under flo-voice1.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-27
- Tools8
- Server calls itselfacp-sandbox
- Server version0.2.0
- Protocol version2025-06-18
On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 479 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 1 of the 7 days it takes to judge reliability.
Once connected
- create_checkout, update_checkout, cancel_checkout change data without a sign-in: anyone with the address can call them.
- Parameters are untyped or undescribed in 6 of 8 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
- Answeredmeasuring1 of the 7 daily checks it takes to print a share
- Median first answer476 ms
- Space in an agent's context≈ 1,086 tokensthe definitions of all its tools (8), which an agent carries on every turn
- Tool definitionsB · 88 of 100
- Typed results0 of 8 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 6 of 8
Worth a look
- Tools that change data, on a server that answers without a sign-in: create_checkout, update_checkout, cancel_checkout
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
list_productsList everything the demo store sells, with product ids and prices. Prices are in USD.
create_checkoutStart a checkout (an Agentic Commerce Protocol checkout session) with the products and quantities the user wants. Returns the session id, the cart and its total. If no api_key is given, a sandbox key is created and returned.
update_checkoutReplace the items in an open checkout (e.g. the user changed their mind). Any PayPal payment created for the old total is dropped.
get_checkoutRead the current cart, total, payment status and order of a checkout.
request_paypal_paymentCreate a PayPal (sandbox) payment for the checkout's exact total. Returns approve_url, the PayPal link where the user approves the payment.
wait_for_payment_approvalWait (up to 45s per call) until PayPal reports the user approved the payment. Returns still_waiting if the user has not approved yet.
complete_checkoutPlace the order. With payment "paypal" the approved PayPal payment is captured first, and the order only goes through if PayPal confirms the money for the exact total. "mock" skips real payment (testing only).
cancel_checkoutCancel an open checkout. Nothing is charged.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"acp-sandbox": {
"type": "http",
"url": "https://acp-sandbox.flo-voice1.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http flo-voice1 https://acp-sandbox.flo-voice1.com/mcpclaude.ai, ChatGPT and other clients: add https://acp-sandbox.flo-voice1.com/mcp as a custom connector in the settings.
- com.flo-voice1/agent-identity-mcpanswers, requires sign-inverified in the MCP registry
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.