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.

com.flo-voice1/acp-sandbox

REMOTE · ACP-SANDBOX.FLO-VOICE1.COM

Agentic Commerce Protocol sandbox: agent builds a cart, human approves a real PayPal payment.

+3 this week 68 Trust /100

Last scanned (5 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 24 Oct 2026.

Category E-commerce

Recent critical change

Authorization (24 Oct 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 Usability64
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 553 tokens (~69/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 50% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 24 Oct 26 +1
    • Authorization: unverified → fail ▼ critical
    • Tool “create_checkout” rewrote its description, which is the text the model reads security
    • Tool “request_paypal_payment” rewrote its description, which is the text the model reads security
    • Tool “update_checkout” rewrote its description, which is the text the model reads security
    • Tool “wait_for_payment_approval” rewrote its description, which is the text the model reads security
    • Tool “cancel_checkout” is now declared destructive security
    • Tool “complete_checkout” is now declared destructive security
    • Tool “update_checkout” is now declared destructive security
  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 +1
    • Stability: unverified → 0.07 ▲ functional
  • 10 Oct 26 61

    First indexed and scored.

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 24 Oct 2026 · Probed https://acp-sandbox.flo-voice1.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=acp-sandbox.flo-voice1.com CN=YE1,O=Let's Encrypt,C=US 26 Aug 2026 24 Nov 2026 ECDSA 256 ECDSA-SHA384 529b84d10ea3a00975639c9fbe4c415d8f4
SANs: acp-sandbox.flo-voice1.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 insecure

Validation of acp-sandbox.flo-voice1.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
flo-voice1.com. absent 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://acp-sandbox.flo-voice1.com/mcp Verified 200
http (plaintext) http://acp-sandbox.flo-voice1.com/mcp HTTPS enforced 301 https://acp-sandbox.flo-voice1.com/mcp
MCP tools · 8 exposed · ~553 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
cancel_checkout ~47

Cancel an open checkout. Nothing is charged.

NameTypeReqDescription
api_keystring–Sandbox key from create_checkout (not needed if the connection already carries one).
session_idstringyes–

No output schema declared.

No examples provided.

complete_checkout ~90

Place 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).

NameTypeReqDescription
api_keystring–Sandbox key from create_checkout (not needed if the connection already carries one).
paymentstring––
session_idstringyes–

No output schema declared.

No examples provided.

create_checkout ~112

Start 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.

NameTypeReqDescription
api_keystring–Sandbox key from create_checkout (not needed if the connection already carries one).
buyer_emailstring–The buyer's email, if the user gave one.
itemsarrayyesProducts to buy, by product_id from list_products.

No output schema declared.

No examples provided.

get_checkout ~53

Read the current cart, total, payment status and order of a checkout.

NameTypeReqDescription
api_keystring–Sandbox key from create_checkout (not needed if the connection already carries one).
session_idstringyes–

No output schema declared.

No examples provided.

list_products ~26

List everything the demo store sells, with product ids and prices. Prices are in USD.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

request_paypal_payment ~70

Create a PayPal (sandbox) payment for the checkout's exact total. Returns approve_url, the PayPal link where the user approves the payment.

NameTypeReqDescription
api_keystring–Sandbox key from create_checkout (not needed if the connection already carries one).
session_idstringyes–

No output schema declared.

No examples provided.

update_checkout ~74

Replace the items in an open checkout (e.g. the user changed their mind). Any PayPal payment created for the old total is dropped.

NameTypeReqDescription
api_keystring–Sandbox key from create_checkout (not needed if the connection already carries one).
itemsarrayyes–
session_idstringyes–

No output schema declared.

No examples provided.

wait_for_payment_approval ~81

Wait (up to 45s per call) until PayPal reports the user approved the payment. Returns still_waiting if the user has not approved yet.

NameTypeReqDescription
api_keystring–Sandbox key from create_checkout (not needed if the connection already carries one).
session_idstringyes–
timeout_secondsinteger––

No output schema declared.

No examples provided.

Install

How do I install the com.flo-voice1/acp-sandbox MCP server?

com.flo-voice1/acp-sandbox is a hosted endpoint at https://acp-sandbox.flo-voice1.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 · acp-sandbox.flo-voice1.com

# add to Claude Code
claude mcp add --transport http com-flo-voice1-acp-sandbox 'https://acp-sandbox.flo-voice1.com/mcp'
Common questions

What is the com.flo-voice1/acp-sandbox MCP server?

com.flo-voice1/acp-sandbox is an MCP server listed in the public MCP registry as com.flo-voice1/acp-sandbox. Agentic Commerce Protocol sandbox: agent builds a cart, human approves a real PayPal payment. This page covers its hosted endpoint (https://acp-sandbox.flo-voice1.com/mcp).

Is the com.flo-voice1/acp-sandbox MCP server safe to use?

com.flo-voice1/acp-sandbox scores 68 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 com.flo-voice1/acp-sandbox MCP server expose?

com.flo-voice1/acp-sandbox exposes 8 tools: list_products, create_checkout, update_checkout, get_checkout, request_paypal_payment, and 3 more. Their descriptions and schemas cost roughly 553 tokens of context every time the server is loaded.

Does the com.flo-voice1/acp-sandbox MCP server require authentication?

No. We connected to com.flo-voice1/acp-sandbox without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.flo-voice1/acp-sandbox MCP server still maintained?

com.flo-voice1/acp-sandbox is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.