Koskamo

Tethered Trust Builders MCP

An MCP server for builders that verifies MCP server functionality, checks directory listings, publishes to the official MCP Registry, validates x402 payment setups, and monitors listing reliability.

Visit Chimes In LLC

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Tethered Trust Builders MCP logo, by Chimes In LLCVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-09Operated by Chimes In LLC
MCP endpoint (Streamable HTTP)
https://tetheredtrust.com/mcp/builders
Vendor documentation

What its tools do

12 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Read-only (9)

Can change data (3)

12 of 12 have a description · 12 of 12 declare behavior hints · 6 of 11 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to tetheredtrust.com ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Verify if an MCP server connects and lists tools correctly
  • Check where a server is listed across multiple registries
  • Publish an MCP server to the official MCP Registry
  • Check if an x402 payment endpoint is configured correctly

Source and maintenance

Vendor evidenceRegistry 0.59.2
mcp-registry: com.tetheredtrust/builders@0.59.2Project website

Protocol and capabilities

Server
tethered-trust-builders 0.60.0
MCP protocol negotiated in check
2025-11-25
Tools
12 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Tools for people who build and sell agent tools. verify_mcp: does an MCP server work (connects, lists tools, checks schemas). launch_check: where a server is listed (official MCP Registry, Glama, x402 Bazaar, npm, PyPI) and the fix plan. publish_to_registry: publish to the official MCP Registry under your domain. check_payment_setup: will agents' x402 payments to an endpoint go through. reliability_score: payment-readiness score of any x402 API before paying it. watch_listing and launch_plan: keep checking every day, with a webhook. verify_page: does a web page actually work. Terms: https://tetheredtrust.com/api-terms.

Tools

12 advertised

how_it_works — How Tethered Trust works
Advertised by the server during the last successful anonymous check.
Advertised read-only

What Tethered Trust is, what it covers, where its data comes from, pricing and terms.

how_it_works input schema
{
  "type": "object",
  "properties": {}
}
how_it_works annotations
{
  "title": "How Tethered Trust works",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
enrich_catalog — Enrich a product catalog
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

For retailers and marketplaces (API key required): up to 50 products per call (SKU with title, URL or GTIN) in; each product's compatibility attributes out (standards it takes and provides, numeric limits, evidence level, freshness), ready to add to a product feed or UCP catalog so agents can match it to what shoppers own.

enrich_catalog input schema
{
  "type": "object",
  "required": [
    "items"
  ],
  "properties": {
    "items": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "id": {
            "type": "string",
            "description": "Your SKU or offer id (echoed back)."
          },
          "url": {
            "type": "string"
          },
          "gtin": {
            "type": "string"
          },
          "brand": {
            "type": "string"
          },
          "model": {
            "type": "string"
          },
          "title": {
            "type": "string"
          }
        }
      },
      "maxItems": 50,
      "minItems": 1
    },
    "research": {
      "type": "boolean",
      "description": "Default true: research up to 10 items per call that aren't in our catalog (from the manufacturer's page)."
    }
  }
}
enrich_catalog annotations
{
  "title": "Enrich a product catalog",
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": false,
  "destructiveHint": false
}
verify_page — Verify a web page works
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

Call this before you tell someone a web page, site or deploy is done or working, or before relying on another agent's "it's live": we open the public page in a separate browser (desktop or mobile) and check what you list. It loads; this text is visible; this link or button leads to this address; no script errors; no broken same-site links. Pass / fail / couldn't-verify per check, with a screenshot and a signed receipt. Read-only: no logins, forms or purchases.

verify_page input schema
{
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Public https:// page to check, e.g. the page you just built or changed."
    },
    "checks": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "type"
        ],
        "properties": {
          "max": {
            "type": "integer",
            "description": "For no_broken_links: how many same-site links to test (default 15, max 25)."
          },
          "text": {
            "type": "string",
            "description": "For text/no_text: exact text that must (or must not) be visible. For link: the visible label of the link or button."
          },
          "type": {
            "enum": [
              "loads",
              "text",
              "no_text",
              "link",
              "no_console_errors",
              "no_broken_links"
            ],
            "type": "string"
          },
          "expect_url": {
            "type": "string",
            "description": "For link: where it should lead (same path or below)."
          }
        }
      },
      "maxItems": 8,
      "description": "What must be true. 'loads' is always included."
    },
    "viewport": {
      "enum": [
        "desktop",
        "mobile"
      ],
      "type": "string",
      "description": "Check as a desktop (1280 px) or phone (390 px) browser. Default desktop."
    },
    "screenshot": {
      "type": "boolean",
      "description": "Return a screenshot link (default true)."
    }
  }
}
verify_page annotations
{
  "title": "Verify a web page works",
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": false,
  "destructiveHint": false
}
verify_mcp — Verify an MCP server works
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

Call this before you recommend, install or rely on an MCP server, after deploying one, or when a connector seems broken: we connect as an MCP client, list its tools, check each has a usable input schema and description, confirm the tools you name exist, and optionally run one sample call on a read-only tool. Pass / fail / couldn't-verify per check with a signed receipt. Never signs in or calls tools that change things.

verify_mcp input schema
{
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "The MCP server's public https:// endpoint (Streamable HTTP), e.g. https://example.com/mcp."
    },
    "call": {
      "type": "object",
      "properties": {
        "tool": {
          "type": "string"
        },
        "arguments": {
          "type": "object"
        },
        "expect_text": {
          "type": "string",
          "description": "Text the reply must contain."
        }
      },
      "description": "Optional sample call. Only made if the server marks the tool read-only (annotations.readOnlyHint)."
    },
    "expect_tools": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 20,
      "description": "Tool names that must be listed."
    }
  }
}
verify_mcp annotations
{
  "title": "Verify an MCP server works",
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": false,
  "destructiveHint": false
}
launch_check — Is this MCP server findable?
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

Call this after building or deploying an MCP server or paid agent API, or when its listings may be out of date: we check it works (as verify_mcp does), then look it up in the official MCP Registry (and whether the listed version is current), Glama, PulseMCP, the x402 Bazaar, npm and PyPI, plus its server card, llms.txt and robots.txt (Smithery, PulseMCP, mcp.so and Claude's directory are listed with links to check by hand). Returns a score, what's missing or stale, an ordered fix plan and a ready-to-publish server.json. Read-only.

launch_check input schema
{
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "npm": {
      "type": "string",
      "description": "Optional: npm package name to check."
    },
    "url": {
      "type": "string",
      "description": "The MCP server's public https:// endpoint, e.g. https://example.com/mcp."
    },
    "name": {
      "type": "string",
      "description": "Optional: the server's display name, to search directories (defaults to the name the server reports)."
    },
    "pypi": {
      "type": "string",
      "description": "Optional: PyPI project name to check."
    },
    "description": {
      "type": "string",
      "description": "Optional: one-line description for the generated server.json (max 100 characters)."
    },
    "registry_name": {
      "type": "string",
      "description": "Optional: its official MCP Registry name, e.g. com.example/server."
    }
  }
}
launch_check annotations
{
  "title": "Is this MCP server findable?",
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": false,
  "destructiveHint": false
}
publish_to_registry — Publish an MCP server to the official registry
Advertised by the server during the last successful anonymous check.
Open-world

Call this to get an MCP server into the official MCP Registry (which Glama, PulseMCP and others import from) without mcp-publisher or DNS: first call with url returns a one-line file to host at https://<domain>/.well-known/mcp-registry-auth; once it's up, call again with publisher_id and we publish server.json under your domain's namespace, then re-publish every new version automatically for 90 days. $5, charged only when we publish. Remove the file to revoke.

publish_to_registry input schema
{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "The MCP server's public https:// endpoint (Streamable HTTP)."
    },
    "slug": {
      "type": "string",
      "description": "Optional: the part after the slash in the registry name."
    },
    "title": {
      "type": "string"
    },
    "domain": {
      "type": "string",
      "description": "Optional: the domain to verify (default: the URL's main domain, e.g. example.com for mcp.example.com). Becomes the namespace (com.example/...)."
    },
    "version": {
      "type": "string",
      "description": "Optional: version to publish (default: the version your server reports)."
    },
    "website": {
      "type": "string"
    },
    "repository": {
      "type": "string"
    },
    "description": {
      "type": "string",
      "description": "One line, max 100 characters."
    },
    "publisher_id": {
      "type": "string",
      "description": "Second call: the publisher_id from the first call, after hosting the proof file."
    }
  }
}
publish_to_registry annotations
{
  "title": "Publish an MCP server to the official registry",
  "readOnlyHint": false,
  "openWorldHint": true,
  "idempotentHint": false,
  "destructiveHint": false
}
check_payment_setup — Will agents' payments go through?
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

Call this after building or changing a paid (x402) endpoint, or when agents' payments fail: we call it unpaid like a paying agent, read the 402, and check the payment request parses (v1 or v2), the token's EIP-712 domain (extra.name/version) matches the contract on-chain (the usual cause of 'invalid signature' payments), network id, amount, payTo, timeout, CORS headers for browser agents, resource URL, description and Bazaar discovery. Pass / warn / fail per check with exact fixes. Never pays.

check_payment_setup input schema
{
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "The paid endpoint's public https:// URL (an x402 resource)."
    },
    "body": {
      "type": "object",
      "description": "Optional example JSON body for POST endpoints."
    },
    "method": {
      "enum": [
        "GET",
        "POST"
      ],
      "type": "string",
      "description": "HTTP method the endpoint expects (default GET)."
    }
  }
}
check_payment_setup annotations
{
  "title": "Will agents' payments go through?",
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": false,
  "destructiveHint": false
}
watch_listing — Watch an MCP server's listings daily
Advertised by the server during the last successful anonymous check.
Open-world

Call this after launching an MCP server or paid agent API to keep it findable: we run launch_check today and every day for 30 days, and tell your webhook (signed) when something changes: the server stops answering, the registry listing falls behind a release, a directory drops it, robots.txt starts blocking. $3 per 30 days; call again with watch_id to renew. Returns today's full launch check.

watch_listing input schema
{
  "type": "object",
  "properties": {
    "npm": {
      "type": "string"
    },
    "url": {
      "type": "string",
      "description": "The MCP server's public https:// endpoint to watch."
    },
    "name": {
      "type": "string"
    },
    "pypi": {
      "type": "string"
    },
    "webhook": {
      "type": "string",
      "description": "Optional public https:// URL: we POST a signed listing.changed event when something changes."
    },
    "watch_id": {
      "type": "string",
      "description": "To renew: an existing watch_id (adds 30 days)."
    },
    "registry_name": {
      "type": "string"
    }
  }
}
watch_listing annotations
{
  "title": "Watch an MCP server's listings daily",
  "readOnlyHint": false,
  "openWorldHint": true,
  "idempotentHint": false,
  "destructiveHint": false
}
reliability_score — Can agents pay this API?
Advertised by the server during the last successful anonymous check.
Advertised read-only

Before paying an unfamiliar x402 API, look up its payment-readiness score (0-100) from our daily unpaid checks of the x402 Bazaar: how many of its endpoints would accept an agent's payment, and the common problems. Free.

reliability_score input schema
{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "Or any URL on that host."
    },
    "host": {
      "type": "string",
      "description": "The paid API's host, e.g. api.example.com."
    }
  }
}
reliability_score annotations
{
  "title": "Can agents pay this API?",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
launch_plan — Keep my MCP server / paid API findable and payable
Advertised by the server during the last successful anonymous check.
Open-world

For sellers: 30 days of official MCP Registry publishing on every new version, a daily listing watch (registry, Glama, x402 Bazaar, npm, PyPI, health) and daily payment checks of up to 10 x402 endpoints, with one signed webhook. $12 per 30 days; renew with plan_id.

launch_plan input schema
{
  "type": "object",
  "properties": {
    "npm": {
      "type": "string"
    },
    "url": {
      "type": "string",
      "description": "Your MCP server's public https:// endpoint (listing watch + registry publishing)."
    },
    "pypi": {
      "type": "string"
    },
    "title": {
      "type": "string"
    },
    "domain": {
      "type": "string"
    },
    "plan_id": {
      "type": "string",
      "description": "To renew: an existing plan_id (adds 30 days to everything)."
    },
    "publish": {
      "type": "boolean",
      "description": "Publish to the official MCP Registry (default true)."
    },
    "webhook": {
      "type": "string",
      "description": "Public https:// URL for signed listing.changed, payment.changed and plan.expiring events."
    },
    "api_host": {
      "type": "string",
      "description": "Host of your paid x402 API, e.g. api.example.com (we use the endpoints the x402 Bazaar lists for it)."
    },
    "endpoints": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "url": {
            "type": "string"
          },
          "body": {
            "type": "object"
          },
          "method": {
            "enum": [
              "GET",
              "POST"
            ],
            "type": "string"
          }
        }
      },
      "maxItems": 10,
      "description": "Or name up to 10 paid endpoints yourself."
    },
    "repository": {
      "type": "string"
    },
    "description": {
      "type": "string"
    }
  }
}
launch_plan annotations
{
  "title": "Keep my MCP server / paid API findable and payable",
  "readOnlyHint": false,
  "openWorldHint": true,
  "idempotentHint": false,
  "destructiveHint": false
}
launch_plan_status — Launch Plan status
Advertised by the server during the last successful anonymous check.
Advertised read-only

Where a Launch Plan stands: listings, registry version and each paid endpoint's payment check. Free.

launch_plan_status input schema
{
  "type": "object",
  "required": [
    "plan_id"
  ],
  "properties": {
    "plan_id": {
      "type": "string"
    }
  }
}
launch_plan_status annotations
{
  "title": "Launch Plan status",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
listing_status — Listing watch status
Advertised by the server during the last successful anonymous check.
Advertised read-only

Where a watched MCP server stands right now: each directory's status, the latest changes, and when the watch ends. Free.

listing_status input schema
{
  "type": "object",
  "required": [
    "watch_id"
  ],
  "properties": {
    "watch_id": {
      "type": "string",
      "description": "The watch_id from watch_listing."
    }
  }
}
listing_status annotations
{
  "title": "Listing watch status",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (2 of 2 answered).

  1. 2026-11-09: 1 of 1 checks answered
  2. 2026-11-10: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
854 ms
95th percentile latency
854 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 854 ms · metadata changed · 12 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http tethered-trust-builders-mcp https://tetheredtrust.com/mcp/builders

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add tethered-trust-builders-mcp --url https://tetheredtrust.com/mcp/builders

Cursor

Merge this server into .cursor/mcp.json in your project, then enable tethered-trust-builders-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "tethered-trust-builders-mcp": {
      "url": "https://tetheredtrust.com/mcp/builders"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "tethered-trust-builders-mcp": {
      "type": "streamableHttp",
      "url": "https://tetheredtrust.com/mcp/builders",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start tethered-trust-builders-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "tethered-trust-builders-mcp": {
      "type": "http",
      "url": "https://tetheredtrust.com/mcp/builders"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http tethered-trust-builders-mcp https://tetheredtrust.com/mcp/builders

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://tetheredtrust.com/mcp/builders

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "tethered-trust-builders-mcp": {
      "serverUrl": "https://tetheredtrust.com/mcp/builders"
    }
  }
}

Let your agent find its tools

Find servers like Tethered Trust Builders MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 9,448

Do you run Tethered Trust Builders MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing