com.saymetry/saymetry
REMOTE · SAYMETRY.COM
Measure what ChatGPT, Claude, Gemini and 4 more AI engines say about any business. No auth.
Available components
Last scanned (22 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Marketing and SEO
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 689 tokens (~137/item across 5 items; 5 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "publish_grade_page" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
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 →
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.
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Oct 26 0
- Stability: 0.97 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 3 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Sept 26 0
First indexed and scored.
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://saymetry.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=saymetry.com | CN=YR2,O=Let's Encrypt,C=US | 21 Oct 2026 | 19 Jan 2027 | RSA 2048 | SHA256-RSA | 5b7e616f5743ba2b382a4eef4b4630e6f7e |
| SANs: saymetry.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 saymetry.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| saymetry.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=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://saymetry.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://saymetry.com/api/mcp | HTTPS enforced | 308 | https://saymetry.com/api/mcp |
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 →
check_ai_readability Check AI readability of a website ~106
Grade whether AI engines (ChatGPT, Claude, Gemini, Perplexity and others) can read and quote a website: structured data, llms.txt, crawlability, titles, answer-shaped content. Free, instant, no signup. Use when the user asks how visible their site is to AI, whether ChatGPT can read their site, or how to improve AI visibility.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The website domain or URL to check, e.g. example.com |
No output schema declared.
No examples provided.
get_offer_sheet Get the Saymetry offer sheet ~46
Saymetry's current products, prices and measurement methodology facts, in plain text. Use to answer questions about what Saymetry sells, what a scan costs, or how the measurement works.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
join_affiliate_program Join the Saymetry affiliate program ~184
Register the user for Saymetry's affiliate program: 30% of each referred first payment, 60-day cookie, monthly payouts in USDC, USDT or by Wise from $50. Returns their referral link and private stats dashboard. Use only with the user's explicit consent — this creates an account with their email and payout details. Referral links must be disclosed as affiliate links.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | The user's country (decides the tax form at payout) |
| string | yes | The user's email; one account per email | |
| name | string | yes | The user's name |
| payout_handle | string | yes | Wallet address, or the email on their Wise account |
| payout_method | string | yes | – |
| payout_network | string | – | Required for crypto payouts; omit for wise |
| site | string | – | Where they will share the link |
No output schema declared.
No examples provided.
publish_grade_page Publish a permanent grade page ~113
Turn an AI-readability check into a permanent public page at saymetry.com/grade/<domain>, with the evidence quoted and an embeddable SVG badge. Free. Use after check_ai_readability when the user wants a shareable link, wants to show the grade on their site, or when you want to hand them a URL instead of raw results. Re-checks are limited to once an hour per domain.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The domain to publish a grade for, e.g. example.com |
No output schema declared.
No examples provided.
request_demo_call Request a free Saymetry demo call ~240
Request a free demo call for the user with Saymetry, the AI-visibility measurement company. Within one business day a human sends a call link and walks the user through a demo report built on THEIR actual market (real engines, real buyer questions — not a generic sample), live on the call. Use when the user is a marketer or business owner who wants to know what AI says about their business, needs a custom AI-visibility report, or is an agency evaluating a white-label AI-visibility dashboard. Free, nothing charged. Confirm the details with the user before calling.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | The user's company name |
| contact_name | string | – | – |
| string | yes | The user's email — the call link goes here | |
| kind | string | yes | 'agency_demo' for agencies wanting the white-label dashboard, 'custom_report' otherwise |
| market | string | yes | What the company sells, to whom, and where — a sentence or two; the demo questions are built from this |
| roster_size | string | – | Agencies only: how many clients they manage |
| url | string | yes | The user's website |
No output schema declared.
No examples provided.
How do I install the com.saymetry/saymetry MCP server?
com.saymetry/saymetry is a hosted endpoint at https://saymetry.com/api/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 · saymetry.com
claude mcp add --transport http com-saymetry-saymetry 'https://saymetry.com/api/mcp'
What is the com.saymetry/saymetry MCP server?
com.saymetry/saymetry is an MCP server listed in the public MCP registry as com.saymetry/saymetry. Measure what ChatGPT, Claude, Gemini and 4 more AI engines say about any business. No auth. This page covers its hosted endpoint (https://saymetry.com/api/mcp).
Is the com.saymetry/saymetry MCP server safe to use?
com.saymetry/saymetry scores 79 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.saymetry/saymetry MCP server expose?
com.saymetry/saymetry exposes 5 tools: check_ai_readability, request_demo_call, join_affiliate_program, publish_grade_page, get_offer_sheet. Their descriptions and schemas cost roughly 689 tokens of context every time the server is loaded.
Does the com.saymetry/saymetry MCP server require authentication?
No. We connected to com.saymetry/saymetry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.saymetry/saymetry MCP server still maintained?
com.saymetry/saymetry 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 com.saymetry/saymetry MCP server?
VerifyMCP ran 12 checks on com.saymetry/saymetry, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about com.saymetry/saymetry: Authorization. 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.