mcp-registry/com.saymetry/saymetry · v0.1.0
As of 2026-10-19 17:24 UTC, the Saymetry MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Measure what ChatGPT, Claude, Gemini and 4 more AI engines say about any business. No auth.
Claude Code
claude mcp add --transport http saymetry-mcp-server https://saymetry.com/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"saymetry-mcp-server": {
"type": "http",
"url": "https://saymetry.com/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
2 parameter(s) across 2 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.saymetry%2Fsaymetry/fixes
{
"name": "check_ai_readability",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"description": "The website domain or URL to check, e.g. example.com"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Check AI readability of a website"
}{
"name": "get_offer_sheet",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
},
"annotations": {
"readOnlyHint": true
},
"title": "Get the Saymetry offer sheet"
}{
"name": "publish_grade_page",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"description": "The domain to publish a grade for, e.g. example.com"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Publish a permanent grade page"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.saymetry/saymetry"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.saymetry/saymetry"}) over MCP.
request_demo_call ~376 tokensjoin_affiliate_program ~332 tokenspublish_grade_page ~175 tokenscheck_ai_readability ~165 tokensget_offer_sheet ~93 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.saymetry%2Fsaymetry?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.saymetry%2Fsaymetry?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.saymetry%2Fsaymetry.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.saymetry%2Fsaymetry.svg :target: https://glimind.com/server/mcp-registry%2Fcom.saymetry%2Fsaymetry?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:6f9008954f6cc0d2…, first seen 2026-10-17, included at leaf 14256 of 27,852. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable finance servers · most reliable web servers · most reliable communication servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-19 17:24 UTC, the Saymetry MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Saymetry MCP server advertises 5 tools, including check_ai_readability, get_offer_sheet, join_affiliate_program, publish_grade_page, request_demo_call.
Point your MCP client at this streamable-http endpoint: https://saymetry.com/api/mcp
Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.