Teppi

xyz.teppiPublished by teppi.xyzOfficial publisherv0.1.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant check what a paid x402 endpoint or MCP server actually delivered, using repeatable probes.

What you can do
Teppi is a remote MCP server that reports on what a paid x402 endpoint or MCP server delivered, based on probes that anyone can repeat. The registry description frames its purpose as verification of delivered results rather than calling the paid service itself. No tool list is published, so the exact operations are not documented in the supplied material.
When to use it
Worth considering when you need to confirm that a paid x402 endpoint or MCP server returned what was expected, and you want evidence that can be reproduced by others rather than a one-off check.
Requirements
A remote streamable HTTP endpoint at the provider's host; no packages, environment variables, or headers are declared. No authentication is declared, though the provider's own documentation may describe additional conditions.
Before you install
The server concerns paid x402 endpoints, so any spending happens on the services being checked, not necessarily here. No credentials are declared, but confirm with the provider what data the probes send and to whom before relying on the results.

Installation

In SourceWeft

  1. Open Teppi in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/xyz.teppi%2Fteppi/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "teppi": {
      "type": "http",
      "url": "https://api.teppi.xyz/mcp"
    }
  }
}

Tools

5

search_capabilities

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.

Parameterssortlimitqueryrequiredmax_usdnetwork

get_capability

One capability in full

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

Parametersidrequired

plan_route

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.

Parametersgoalrequiredmin_gradebudget_usdrequired

check_grade

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.

Parametersmethodpay_toid_or_urlrequired

check_exposure

What your paid dependencies deliver

Look up every paid endpoint your agents call in one go, added up by the address each one pays: which are unknown to the record, which took money and returned nothing, which list what they do not serve, and how much monthly spend sits on each. Unknown is reported as unknown, never as bad.

Parametersdependenciesrequired

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.