# Teppi (remote · api.teppi.xyz)

Check what a paid x402 endpoint or MCP server delivered, from probes anyone can repeat.

- Trust score: 65/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `api.teppi.xyz`: 65/100 (this document), [markdown](https://verifymcp.io/servers/xyz-teppi-teppi/api.md), [page](https://verifymcp.io/servers/xyz-teppi-teppi/api)

## Channel facts

- Endpoint: `https://api.teppi.xyz/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

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

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 353 tokens (~88/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Teppi MCP server?

Teppi is a hosted endpoint at https://api.teppi.xyz/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 xyz-teppi-teppi 'https://api.teppi.xyz/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "xyz-teppi-teppi": {
      "url": "https://api.teppi.xyz/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "xyz-teppi-teppi": {
      "type": "http",
      "url": "https://api.teppi.xyz/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.xyz-teppi-teppi]
url = "https://api.teppi.xyz/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add xyz-teppi-teppi --url 'https://api.teppi.xyz/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  xyz-teppi-teppi:
    url: "https://api.teppi.xyz/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "xyz-teppi-teppi": {
      "Transport": "http",
      "Url": "https://api.teppi.xyz/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add xyz-teppi-teppi -t streamable-http -u 'https://api.teppi.xyz/mcp'
```

### Other

```json
{
  "mcpServers": {
    "xyz-teppi-teppi": {
      "type": "http",
      "url": "https://api.teppi.xyz/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-09-20 (score 65, 0)

- [security] Tool “check_grade” rewrote its description, which is the text the model reads
- [cosmetic] “check_grade” added an optional parameter “method”

### 2026-09-19 (score 65, +1)

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

### 2026-09-17 (score 64, +1)

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

### 2026-09-15 (score 63, +1)

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

### 2026-09-12 (score 62, +1)

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

### 2026-09-10 (score 61, +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.

### 2026-09-09 (score 60, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-09-08 (score 60, +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.

## MCP tools (4)

### `search_capabilities` (~106 tokens)

Search paid capabilities

Search paid agent capabilities by task description. Returns the price, the input and output schemas, the networks each one settles on, and what has been verified about it. Sort by verified to put the ones with the most evidence behind them first. Use before paying an x402 endpoint you have not used.

Input parameters:

- `limit` (integer)
- `max_usd` (string)
- `network` (string)
- `query` (string, required)
- `sort` (string)

### `get_capability` (~40 tokens)

One capability in full

Full detail for one capability: schemas, pricing, networks, the seller behind it, and every observation recorded against it.

Input parameters:

- `id` (string, required)

### `plan_route` (~80 tokens)

Plan a route

Turn a goal and a budget into an ordered list of paid endpoints that could reach it, with a cost estimate and what has been verified about each step. Moves no money and buys nothing: it returns the plan for you to run yourself.

Input parameters:

- `budget_usd` (string, required)
- `goal` (string, required)
- `min_grade` (string)

### `check_grade` (~95 tokens)

What has been verified

Return what has been verified about an x402 endpoint or its url: whether it answers, what it charges, and whether that price has moved. Answers unrated rather than guessing when the evidence is thin. Works for endpoints Teppi does not operate, and a url never seen is put in line for a free handshake, so ask again in an hour.

Input parameters:

- `id_or_url` (string, required)
- `method` (string)

## Diagnostics

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

## Score history

- 2026-09-20: 65
- 2026-09-19: 65
- 2026-09-18: 64
- 2026-09-17: 64
- 2026-09-16: 63
- 2026-09-15: 63
- 2026-09-14: 62
- 2026-09-13: 62
- 2026-09-12: 62
- 2026-09-11: 61
- 2026-09-10: 61
- 2026-09-09: 60
- 2026-09-08: 60
- 2026-09-07: 59
- 2026-09-06: 59
- 2026-09-05: 59
- 2026-09-04: 59

## Common questions

### What is the Teppi MCP server?

Teppi is an MCP server listed in the public MCP registry as xyz.teppi/teppi. Check what a paid x402 endpoint or MCP server delivered, from probes anyone can repeat. This page covers its hosted endpoint (https://api.teppi.xyz/mcp).

### Is the Teppi MCP server safe to use?

Teppi scores 65 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 Teppi MCP server expose?

Teppi exposes 4 tools: search_capabilities, get_capability, plan_route, check_grade. Their descriptions and schemas cost roughly 321 tokens of context every time the server is loaded.

### Does the Teppi MCP server require authentication?

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

### Is the Teppi MCP server still maintained?

Teppi is still listed as active in the MCP registry. We last reached this channel on 20 September 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.teppi.xyz/mcp
- Website: https://api.teppi.xyz/docs/verification-method
- Changelog RSS feed: https://verifymcp.io/servers/xyz-teppi-teppi/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/xyz-teppi-teppi/api.json
- HTML version of this page: https://verifymcp.io/servers/xyz-teppi-teppi/api