# Stophy (remote · api.stophy.dev)

One API for live, structured web data. REST, MCP, SDK and CLI.

- Trust score: 79/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-03

## Components

- remote · `api.stophy.dev`: 79/100 (this document), [markdown](https://verifymcp.io/servers/stophydotdev-mcp/api.md), [page](https://verifymcp.io/servers/stophydotdev-mcp/api)
- remote · `mcp.stophy.dev`: 39/100, [markdown](https://verifymcp.io/servers/stophydotdev-mcp/mcp.md), [page](https://verifymcp.io/servers/stophydotdev-mcp/mcp)
- npm · `@stophy/mcp`: 44/100, [markdown](https://verifymcp.io/servers/stophydotdev-mcp/stophy-mcp.md), [page](https://verifymcp.io/servers/stophydotdev-mcp/stophy-mcp)

## Channel facts

- Endpoint: `https://api.stophy.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.0.8`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-03.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 86/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Tools include usage examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (33% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http stophydotdev-mcp 'https://api.stophy.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "stophydotdev-mcp": {
      "url": "https://api.stophy.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "stophydotdev-mcp": {
      "type": "http",
      "url": "https://api.stophy.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.stophydotdev-mcp]
url = "https://api.stophy.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "stophydotdev-mcp": {
      "type": "remote",
      "url": "https://api.stophy.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add stophydotdev-mcp --url 'https://api.stophy.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  stophydotdev-mcp:
    url: "https://api.stophy.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "stophydotdev-mcp": {
      "Transport": "http",
      "Url": "https://api.stophy.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add stophydotdev-mcp -t streamable-http -u 'https://api.stophy.dev/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-03 (score 79, 0)

- [security] 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

### 2026-10-02 (score 79, +7)

- [security improvement] HSTS header: fail → pass
- [security improvement] 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
- [functional improvement] Schema quality: 201 → 159
- [functional improvement] Schema quality: fail → pass
- [cosmetic] “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”

### 2026-10-01 (score 72, 0)

- [security] 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
- [functional] Schema quality: excellent → good
- [cosmetic] “stophy_call” reworded the description of “fields”

### 2026-09-30 (score 72, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [cosmetic] “stophy_call” reworded the description of “fields”
- [cosmetic] “stophy_call” dropped the optional parameter “format”

### 2026-09-29 (score 71, +6)

- [security improvement] 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
- [functional regression] Schema quality: pass → fail
- [functional improvement] Stability: unverified → 0.03
- [functional improvement] Tool “stophy_call” now declares an output schema
- [functional] First check of Tool coverage: 33
- [cosmetic] “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

### 2026-09-28 (score 65)

First indexed and scored.

## MCP tools (3)

### `stophy_search_endpoints` (~95 tokens)

Find Stophy endpoints

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.

Input parameters:

- `category` (string): Source name, such as reddit or youtube.
- `query` (string): What you want in plain words, such as "restaurant reviews in Austin".

### `stophy_describe_endpoint` (~40 tokens)

Describe a Stophy endpoint

Optional: full inputs, filter notes, an example and output fields.

Input parameters:

- `id` (string, required): Endpoint id from stophy_search_endpoints.

### `stophy_call` (~108 tokens)

Call a Stophy endpoint

Get the data from the endpoint you chose, with the credits used.

Input parameters:

- `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, required): Endpoint id from stophy_search_endpoints.
- `input` (object): JSON body for that endpoint. Omit keys you are not setting.

Output parameters:

- `creditsUsed` (number)
- `data`: The endpoint's result. Its shape is in stophy_describe_endpoint.
- `requestId` (string)
- `success` (boolean)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/stophydotdev-mcp/api#diagnostics

## Score history

- 2026-10-03: 79
- 2026-10-02: 79
- 2026-10-01: 72
- 2026-09-30: 72
- 2026-09-29: 71
- 2026-09-28: 65

## Common questions

### 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.

## Links

- Remote endpoint: https://api.stophy.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/stophydotdev-mcp/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/stophydotdev-mcp/api.json
- HTML version of this page: https://verifymcp.io/servers/stophydotdev-mcp/api