agent · model context protocol (mcp)

VirtualSMS

virtualsms.ioevidence retrieved Aug 1, 2026view as JSON all model context protocol (mcp) entries 4 alternatives

ThinFewer than 12 fields evidenced — this vendor discloses little, or we have read little of it

11 fields evidenced · 44 with no public information. Every value below links to the document it came from and the date we checked it.

8 of those are quoted but not yet interpreted: we hold the source sentence and the date we read it, but nobody has written the answer to the question yet. Those rows show the quote and say so rather than repeating it back as an answer. Why these exist

1 of the evidenced values quotes wording our own later capture of the same page no longer contains. Marked below, awaiting an editor.

Also appears in

AI agents that support the Model Context Protocol

Trust gap

How this is scored

These scores are automated. A 1 or 2 counts how many fields this entry answers with a citation — not what those answers say. A 0 means every field for that dimension is recorded as undisclosed and none of the pages we captured mentions it. No one has scored this entry against the rubric yet.

Runtime governance

unscored

Are scope, spend, and authority enforced while the agent runs?

Audit trail

unscored

Is there a tamper-evident record of what it actually did?

Compliance

unscored

Are compliance obligations attached per engagement?

Outcome settlement

1/3 auto

Does payment depend on a verified result?

Scored from 1 evidenced field(s): outcome_based_pricing. Automated score; capped at 2 pending review.

Counts Outcome-based pricing, each cited below.

Insurance & indemnity

unscored

Can the deployment be insured, and is the customer indemnified?

Assurance

Insurance available: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Insurance carriers: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Coverage limits: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Indemnification: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Liability cap: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Audit trail: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Tamper-evident log: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Explainability: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Runtime governance: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Permission scopes: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Compliance certifications: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Regulatory alignment: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Outcome-based pricing: not yet interpreted
“Auto-refund if no SMS”
virtualsms.io · checked Aug 1, 2026
Settlement mechanism: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Dispute process: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
SLA terms: not yet interpreted
“Most SMS verification codes arrive in 30-60 seconds after the app sends the message.”
virtualsms.io · checked Aug 1, 2026
Evaluation coverage: not yet interpreted
“Rated 4.8/5 by customers across Trustpilot and direct reviews.”
virtualsms.io · checked Aug 1, 2026

Agency

Autonomy level: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Human oversight: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Goal complexity: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Action space: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Operating environment: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Initiative: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this

Safety

Safety evaluations: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Red teaming: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Safety policy: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Usage restrictions: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Model or system card: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Incident reporting: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Third-party evaluations: not yet interpreted
“Rated 4.8/5 by customers across Trustpilot and direct reviews.”
virtualsms.io · checked Aug 1, 2026
Data handling: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this

Practicality

Pricing model: Pay as you go
“Pay as you go No subscriptions. Top up via crypto or SBP and pay only for what you use.”
virtualsms.io · checked Aug 1, 2026
Price point: $0.05 /code
“Verifications One-time verification code $0.05 /code Starting from • varies by service & country”
Not in our latest capture. This quote was on the page when we filed it. We captured the same page again on Sep 17, 2026 and it was not there. The value above has not been re-checked by an editor yet. How we re-check citations
virtualsms.io · checked Aug 1, 2026
Availability: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Deployment options: Pay-as-you-go via x402 USDC deposits or prepaid API keys
“Developers & AI Agents Real-SIM SMS verification for AI agents. One canonical endpoint for agents to receive OTP codes across 145+ countries and 2,500+ services. Pay-as-you-go via x402 USDC deposits or prepaid API keys.”
virtualsms.io · checked Aug 1, 2026
Integrations: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Supported regions: not yet interpreted
“145+ countries”
virtualsms.io · checked Aug 1, 2026
Support model: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this

Foundation models

Base models: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Model provider: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Model swappable: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Open weights: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Fine-tuning: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Context window: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this

Ecosystem

Protocols supported: not yet interpreted
“REST API + MCP”
virtualsms.io · checked Aug 1, 2026
Tool use: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Multi-agent: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
API access: not yet interpreted
“Developers can use the REST API for number orders, status checks, SMS webhooks, and cancellation flows.”
virtualsms.io · checked Aug 1, 2026
Open source: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Marketplace presence: not yet interpreted
“Listed on AI Agents Directory Pipedream Glama MCP.so Smithery”
virtualsms.io · checked Aug 1, 2026

Impact

User base: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Deployment scale: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Target sectors: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
High-risk domains: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this
Documented incidents: no public information
virtualsms.io · checked Aug 1, 2026 · source did not state this

Compared with

Side-by-side on the fields where VirtualSMS and the other entry are both on record and actually differ.