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.

Stamped Sidewalks

REMOTE · STAMPEDSIDEWALKS.COM

Price custom concrete stamps from their words or size, search templates, track orders.

−1 this week 70 Trust /100

Last scanned (13 hours ago)

Scores higher than 55% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

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 Usability60
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 577 tokens (~192/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: schema churn in the 7 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage89
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 67% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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.

  • 21 Nov 26 −4
    • Stability: 0.20 → fail ▼ security
    • A breaking change shipped without a version bump: still 1.1.0 ▼ security
    • Tool “search_stamp_templates” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 161 → 192 ▼ functional
  • 20 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 26 +1

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

  • 15 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 14 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://stampedsidewalks.com/api/mcp/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.stampedsidewalks.com CN=YR2,O=Let's Encrypt,C=US 8 Oct 2026 6 Jan 2027 RSA 2048 SHA256-RSA 6ee2e51e30ab84966df91241af3da248ff6
SANs: *.stampedsidewalks.com, stampedsidewalks.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of stampedsidewalks.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
stampedsidewalks.com. 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; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' blob: https://js.stripe.com https://*.sentry.io https://www.googletagmanager.com https://www.googleadservices.com https://googleads.g.doubleclick.net https://connect.facebook.net https://bzrcdn.openai.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com data:; img-src 'self' data: blob: https://*.supabase.co https://www.google-analytics.com https://www.googletagmanager.com https://www.google.com https://*.doubleclick.net https://www.googleadservices.com https://www.facebook.com; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://api.stripe.com https://*.sentry.io https://*.google-analytics.com https://*.analytics.google.com https://www.googletagmanager.com https://stats.g.doubleclick.net https://www.googleadservices.com https://googleads.g.doubleclick.net https://www.google.com https://pagead2.googlesyndication.com https://www.facebook.com https://bzr.openai.com https:
x-content-type-options nosniff
referrer-policy no-referrer

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://stampedsidewalks.com/api/mcp/mcp Verified 200
http (plaintext) http://stampedsidewalks.com/api/mcp/mcp HTTPS enforced 308 https://stampedsidewalks.com/api/mcp/mcp
MCP tools · 3 exposed · ~495 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
calculate_stamp_price ~177

Calculate the price of a custom concrete stamp from its outer dimensions. Uses the same formula as checkout. Dimensions are in inches, each at least 6", with one side 46" or less and the other 94" or less. Plates are cut in whole inches, so a fractional size is quoted (and returned) rounded up. When you have the words rather than a size, call quote_inscription instead: the size comes from the lettering. Excludes shipping and tax.

NameTypeReqDescription
height_inchesnumberyesStamp height in inches. The stamp must have one side 46" or less and the other 94" or less.
quantityinteger––
width_inchesnumberyesStamp width in inches. The stamp must have one side 46" or less and the other 94" or less.

No output schema declared.

No examples provided.

quote_inscription ~266

Price a custom concrete stamp from the words on it. Send the lines (and optionally a font and letter height); get back the measured stamp size in inches, the exact price (the same measurement and rounding the designer and checkout use), a standard shipping estimate, how far ahead of a pour to order, any problems that would stop the order, and design_url: a link that opens exactly this design in the free 3D designer, where the person orders it. Excludes tax.

NameTypeReqDescription
depth_inches––Impression depth in inches: 0.25 (standard, the default) or 0.125 for cities that specify a 1/8" impression. Same price.
fontstring–Font key; default arial-rounded (the designer's default)
letter_height_inchesnumber–Capital-letter height in inches. Omit to use the designer's default (1.75"), stepped down in 0.25" steps to the font's floor if the stamp wouldn't otherwise have one side 46" or less and the other 94…
linesarrayyesThe stamp's words, one array entry per line (1-8 lines, each at most 60 characters). An empty string is a blank line.

No output schema declared.

No examples provided.

track_order ~52

Look up the status of an existing order. Requires both the order number and the email address on the order (both are on the confirmation email).

NameTypeReqDescription
emailstringyes–
order_numberstringyes–

No output schema declared.

No examples provided.

Install

How do I install the Stamped Sidewalks MCP server?

Stamped Sidewalks is a hosted endpoint at https://stampedsidewalks.com/api/mcp/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 · stampedsidewalks.com

# add to Claude Code
claude mcp add --transport http com-stampedsidewalks-stamped-sidewalks 'https://stampedsidewalks.com/api/mcp/mcp'
Common questions

What is the Stamped Sidewalks MCP server?

Stamped Sidewalks is an MCP server listed in the public MCP registry as com.stampedsidewalks/stamped-sidewalks. Price custom concrete stamps from their words or size, search templates, track orders. This page covers its hosted endpoint (https://stampedsidewalks.com/api/mcp/mcp).

Is the Stamped Sidewalks MCP server safe to use?

Stamped Sidewalks scores 70 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 Stamped Sidewalks MCP server expose?

Stamped Sidewalks exposes 3 tools: quote_inscription, calculate_stamp_price, track_order. Their descriptions and schemas cost roughly 495 tokens of context every time the server is loaded.

Does the Stamped Sidewalks MCP server require authentication?

No. We connected to Stamped Sidewalks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Stamped Sidewalks MCP server still maintained?

Stamped Sidewalks 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 Stamped Sidewalks MCP server?

VerifyMCP ran 13 checks on Stamped Sidewalks, 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.