Stophy
REMOTE · API.STOPHY.DEV · 3 COMPONENTS · SCANNED OCT 4
One API for live, structured web data. REST, MCP, SDK and CLI.
Available components
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 Security83
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 504 tokens (~168/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Tools include usage examples.Pass
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (33% of tools); any adoption earns full credit.Pass
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
How do I install the Stophy MCP server?
Stophy is a hosted endpoint at https://api.stophy.dev/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 · api.stophy.dev
claude mcp add --transport http stophydotdev-mcp 'https://api.stophy.dev/mcp'
{
"mcpServers": {
"stophydotdev-mcp": {
"url": "https://api.stophy.dev/mcp"
}
}
} {
"servers": {
"stophydotdev-mcp": {
"type": "http",
"url": "https://api.stophy.dev/mcp"
}
}
} [mcp_servers.stophydotdev-mcp] url = "https://api.stophy.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"stophydotdev-mcp": {
"type": "remote",
"url": "https://api.stophy.dev/mcp",
"enabled": true
}
}
} openclaw mcp add stophydotdev-mcp --url 'https://api.stophy.dev/mcp' --transport streamable-http
mcp_servers:
stophydotdev-mcp:
url: "https://api.stophy.dev/mcp" {
"McpServers": {
"stophydotdev-mcp": {
"Transport": "http",
"Url": "https://api.stophy.dev/mcp"
}
}
} assistant mcp add stophydotdev-mcp -t streamable-http -u 'https://api.stophy.dev/mcp'
{
"mcpServers": {
"stophydotdev-mcp": {
"type": "http",
"url": "https://api.stophy.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “stophy_search_endpoints” rewrote its description, which is the text the model reads security
- Tool “stophy_describe_endpoint” rewrote its description, which is the text the model reads security
- 2 Oct 26 +7
- HSTS header: fail → pass ▲ security
- DNSSEC: fail → pass ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: stophy → Stophy security
- Tool “stophy_call” rewrote its description, which is the text the model reads security
- Tool “stophy_search_endpoints” rewrote its description, which is the text the model reads security
- Schema quality: 201 → 159 ▲ functional
- Schema quality: fail → pass ▲ functional
- “stophy_call” reworded the description of “fields” cosmetic
- “stophy_call” reworded the description of “id” cosmetic
- “stophy_describe_endpoint” reworded the description of “id” cosmetic
- “stophy_search_endpoints” reworded the description of “query” cosmetic
- 1 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “stophy_search_endpoints” rewrote its description, which is the text the model reads security
- Schema quality: excellent → good functional
- “stophy_call” reworded the description of “fields” cosmetic
- 30 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- “stophy_call” reworded the description of “fields” cosmetic
- “stophy_call” dropped the optional parameter “format” cosmetic
- 29 Sept 26 +6
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “stophy_call” rewrote its description, which is the text the model reads security
- Tool “stophy_describe_endpoint” rewrote its description, which is the text the model reads security
- Tool “stophy_search_endpoints” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Tool “stophy_call” now declares an output schema ▲ functional
- First check of Tool coverage: 33 functional
- “stophy_call” added an optional parameter “fields” cosmetic
- “stophy_call” reworded the description of “format” cosmetic
- “stophy_call” reworded the description of “id” cosmetic
- “stophy_describe_endpoint” reworded the description of “id” cosmetic
- “stophy_search_endpoints” reworded the description of “category” cosmetic
- “stophy_search_endpoints” reworded the description of “query” cosmetic
- Tool “stophy_search_endpoints” changed its title: Find Stophy endpoints cosmetic
- Tool “stophy_describe_endpoint” changed its title: Describe a Stophy endpoint cosmetic
- Tool “stophy_call” changed its title: Call a Stophy endpoint cosmetic
- 28 Sept 26 65
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 3 Oct 2026 · Probed https://api.stophy.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.stophy.dev | CN=YE2,O=Let's Encrypt,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5b208f1a536d36a6e92dff20f3fbad5a1f2 |
| SANs: api.stophy.dev | ||||||
| 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 secure
Validation of api.stophy.dev. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| stophy.dev. | present | 2371 | 13 | Verified |
| api.stophy.dev. | Verified address RRset verified with the apex keys |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.stophy.dev/mcp | Verified | 200 | |
| http (plaintext) | http://api.stophy.dev/mcp | HTTPS enforced | 301 | https://api.stophy.dev/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 →
stophy_call Call a Stophy endpoint ~108
Get the data from the endpoint you chose, with the credits used.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Keys to keep, such as ["title", "url"]. They apply to each row of a results list, otherwise to the response. Dot paths reach nested keys, such as "comments.author". Unknown names are rejected. |
| id | string | yes | Endpoint id from stophy_search_endpoints. |
| input | object | – | JSON body for that endpoint. Omit keys you are not setting. |
| Name | Type | Req | Description |
|---|---|---|---|
| creditsUsed | number | yes | – |
| data | – | yes | The endpoint's result. Its shape is in stophy_describe_endpoint. |
| requestId | string | yes | – |
| success | boolean | yes | – |
{"fields":["title","url"],"id":"redditSearch","input":{"query":"bun runtime"}}stophy_describe_endpoint Describe a Stophy endpoint ~40
Optional: full inputs, filter notes, an example and output fields.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Endpoint id from stophy_search_endpoints. |
No output schema declared.
{"id":"youtubeSearch"}stophy_search_endpoints Find Stophy endpoints ~95
Use this first when the user wants live data from the web: search, video, social, places, jobs, shopping, homes, apps, travel or ads. Returns matches with inputs, filters and cost, ready for stophy_call.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Source name, such as reddit or youtube. |
| query | string | – | What you want in plain words, such as "restaurant reviews in Austin". |
No output schema declared.
{"query":"recent reddit posts about bun"}{"category":"youtube"}What is the Stophy MCP server?
Stophy is an MCP server listed in the public MCP registry as io.github.stophydotdev/mcp. One API for live, structured web data. REST, MCP, SDK and CLI. This page covers its hosted endpoint (https://api.stophy.dev/mcp).
Is the Stophy MCP server safe to use?
Stophy 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 Stophy MCP server expose?
Stophy exposes 3 tools: stophy_search_endpoints, stophy_describe_endpoint, stophy_call. Their descriptions and schemas cost roughly 243 tokens of context every time the server is loaded.
Does the Stophy MCP server require authentication?
No. We connected to Stophy without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Stophy MCP server still maintained?
Stophy is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.