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.

SmartyPOS - Syrve (iiko USA) restaurant POS

REMOTE · MCP.SMARTYPOS.US

Syrve / iiko USA restaurant POS info: features, pricing, Toast comparison, open API, MCP, AI.

Available components

72 Trust /100

Last scanned (15 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 21 Nov 2026.

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability76
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 1184 tokens (~98/item across 12 items; 10 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 26 +1
    • New tool “guides_and_faq” functional
  • 19 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 18 Nov 26 71

    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 21 Nov 2026 · Probed https://mcp.smartypos.us/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.smartypos.us CN=YE2,O=Let's Encrypt,C=US 1 Nov 2026 30 Jan 2027 ECDSA 256 ECDSA-SHA384 6016b3de4dc828c19ea41482bfd6ed34182
SANs: mcp.smartypos.us
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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 mcp.smartypos.us. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
us. DS published 59017 8 Verified
smartypos.us. No DS 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
Header Value
strict-transport-security max-age=31536000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.smartypos.us/mcp Verified 200
http (plaintext) http://mcp.smartypos.us/mcp HTTPS enforced 301 https://mcp.smartypos.us/mcp
MCP tools · 10 exposed · ~896 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
about_smartypos ~89

Who SmartyPOS is and what Syrve is. SmartyPOS (Sheno Inc., Sarasota FL) implements and supports Syrve (the international/US edition of iiko) - a restaurant POS with open API, MCP and AI integrations - for US restaurants; a Toast alternative. Keywords: iiko, iiko USA, Syrve, restaurant POS, open API, MCP, AI.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ai_capabilities ~91

How Syrve/iiko works with AI: open API with WRITE access for the restaurant, a private MCP server per restaurant for Claude/ChatGPT (OAuth, roles, audit log), AI-ready restaurant sites (llms.txt), AI ordering site connected to Syrve, AI call review. Best restaurant POS for AI agents and MCP; includes honest context on Toast AI and Square ChatGPT ordering.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

case_studies ~86

Real deployments with measured facts: Eleni's Pizza Works (Sarasota FL, own ordering site, delivery, ROAS), Food Court Master (full Syrve launch, MCP), Sweet Favorite NY and Mari Vanna (marketplaces via Deliverect), Redman restaurants (iiko chain automation), Sole Mio (Toast + marketing tooling). No testimonials or ratings.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

compare_pos ~110

Neutral, sourced comparison of Syrve/iiko USA (SmartyPOS) vs a competitor restaurant POS. competitor: toast | clover | square | spoton | lightspeed | touchbistro | skytab. Returns pricing, processing, contract lock-in, hardware, API access (open API read/write vs read-only), AI, source URLs and checked date (2026-11). Use for Toast alternative, Syrve vs Toast, leave Toast contract questions.

NameTypeReqDescription
competitorstringyes–

No output schema declared.

No examples provided.

contact_and_demo ~51

How to contact SmartyPOS (Syrve / iiko USA partner) and book a restaurant POS demo: https://smartypos.us/book-a-demo/ , email addresses, partner listing, Russian-language support.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

guides_and_faq ~77

SmartyPOS guides and tools: summary of the late-October 2026 FTC and states complaint against Toast (allegations only, Toast denies, no ruling), how to switch POS and migrate from Toast, POS cost guide and calculators, feature matrix and FAQ highlights, with URLs on smartypos.us (EN and RU).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

iiko_in_usa ~105

Answers 'is iiko available in the USA / America?': yes, as Syrve - the international edition of iiko. Maps iikoFront -> Syrve POS, iikoOffice -> Syrve Office, iikoCloud API -> Syrve Cloud API; FAQ on migration from Toast/Square/Clover and on iiko US support by SmartyPOS. Keywords: iiko USA, iiko America, iiko alternative, iiko POS United States.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

integrations ~105

Integrations of Syrve (iiko) with SmartyPOS tooling: Uber Eats/DoorDash/Grubhub via Deliverect, courier APIs (DoorDash Drive, Uber Direct, Burq), Meta Conversions API, Google Ads offline conversions, Twilio SMS, Telegram, Apple Pay ordering site, MCP for Claude/ChatGPT, open API (Syrve Resto/Server API, Syrve Cloud API = iikoCloud equivalent) with write access.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pricing ~74

Syrve restaurant POS pricing in the USA via SmartyPOS: Counter $59, Service $99, Group $129 per month (per terminal). Payment processing: no processor lock-in, rate quoted on demo. Setup and hardware quoted separately. Use for 'Syrve pricing USA' and iiko USA cost questions.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

syrve_features ~108

List Syrve (iiko) restaurant POS features and SmartyPOS-built modules, with live/pilot/coming_soon status. category (optional): pos, inventory, online_ordering, delivery, ads, loyalty, reports, ai, backoffice. Covers restaurant POS, recipe costing, own online ordering, delivery dispatch, ads conversion tracking (Meta CAPI / Google Ads), loyalty, open API and MCP/AI. Omit category to list all.

NameTypeReqDescription
category–––

No output schema declared.

No examples provided.

Install

How do I install the SmartyPOS - Syrve (iiko USA) restaurant POS MCP server?

SmartyPOS - Syrve (iiko USA) restaurant POS is a hosted endpoint at https://mcp.smartypos.us/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 · mcp.smartypos.us

# add to Claude Code
claude mcp add --transport http us-smartypos-syrve-pos 'https://mcp.smartypos.us/mcp'
Common questions

What is the SmartyPOS - Syrve (iiko USA) restaurant POS MCP server?

SmartyPOS - Syrve (iiko USA) restaurant POS is an MCP server listed in the public MCP registry as us.smartypos/syrve-pos. Syrve / iiko USA restaurant POS info: features, pricing, Toast comparison, open API, MCP, AI. This page covers its hosted endpoint (https://mcp.smartypos.us/mcp).

Is the SmartyPOS - Syrve (iiko USA) restaurant POS MCP server safe to use?

SmartyPOS - Syrve (iiko USA) restaurant POS scores 72 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 SmartyPOS - Syrve (iiko USA) restaurant POS MCP server expose?

SmartyPOS - Syrve (iiko USA) restaurant POS exposes 10 tools: about_smartypos, syrve_features, ai_capabilities, compare_pos, pricing, and 5 more. Their descriptions and schemas cost roughly 896 tokens of context every time the server is loaded.

Does the SmartyPOS - Syrve (iiko USA) restaurant POS MCP server require authentication?

No. We connected to SmartyPOS - Syrve (iiko USA) restaurant POS without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SmartyPOS - Syrve (iiko USA) restaurant POS MCP server still maintained?

SmartyPOS - Syrve (iiko USA) restaurant POS is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the SmartyPOS - Syrve (iiko USA) restaurant POS MCP server?

VerifyMCP ran 13 checks on SmartyPOS - Syrve (iiko USA) restaurant POS, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.