Skip to main content
Glama

Tethered Trust for builders

Server Details

Launch and keep agent tools working: MCP checks, registry publishing, x402 payment checks.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

Score is being calculated.

Available Tools

12 tools
check_payment_setupWill agents' payments go through?
Read-only
Inspect

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.

NameRequiredDescriptionDefault
urlYesThe paid endpoint's public https:// URL (an x402 resource).
bodyNoOptional example JSON body for POST endpoints.
methodNoHTTP method the endpoint expects (default GET).
enrich_catalogEnrich a product catalog
Read-only
Inspect

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.

NameRequiredDescriptionDefault
itemsYes
researchNoDefault true: research up to 10 items per call that aren't in our catalog (from the manufacturer's page).
how_it_worksHow Tethered Trust works
Read-onlyIdempotent
Inspect

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

NameRequiredDescriptionDefault

No parameters

launch_checkIs this MCP server findable?
Read-only
Inspect

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.

NameRequiredDescriptionDefault
npmNoOptional: npm package name to check.
urlYesThe MCP server's public https:// endpoint, e.g. https://example.com/mcp.
nameNoOptional: the server's display name, to search directories (defaults to the name the server reports).
pypiNoOptional: PyPI project name to check.
descriptionNoOptional: one-line description for the generated server.json (max 100 characters).
registry_nameNoOptional: its official MCP Registry name, e.g. com.example/server.
launch_planKeep my MCP server / paid API findable and payableInspect

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.

NameRequiredDescriptionDefault
npmNo
urlNoYour MCP server's public https:// endpoint (listing watch + registry publishing).
pypiNo
titleNo
domainNo
plan_idNoTo renew: an existing plan_id (adds 30 days to everything).
publishNoPublish to the official MCP Registry (default true).
webhookNoPublic https:// URL for signed listing.changed, payment.changed and plan.expiring events.
api_hostNoHost of your paid x402 API, e.g. api.example.com (we use the endpoints the x402 Bazaar lists for it).
endpointsNoOr name up to 10 paid endpoints yourself.
repositoryNo
descriptionNo
launch_plan_statusLaunch Plan status
Read-onlyIdempotent
Inspect

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

NameRequiredDescriptionDefault
plan_idYes
listing_statusListing watch status
Read-onlyIdempotent
Inspect

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

NameRequiredDescriptionDefault
watch_idYesThe watch_id from watch_listing.
publish_to_registryPublish an MCP server to the official registryInspect

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:///.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.

NameRequiredDescriptionDefault
urlNoThe MCP server's public https:// endpoint (Streamable HTTP).
slugNoOptional: the part after the slash in the registry name.
titleNo
domainNoOptional: the domain to verify (default: the URL's main domain, e.g. example.com for mcp.example.com). Becomes the namespace (com.example/...).
versionNoOptional: version to publish (default: the version your server reports).
websiteNo
repositoryNo
descriptionNoOne line, max 100 characters.
publisher_idNoSecond call: the publisher_id from the first call, after hosting the proof file.
reliability_scoreCan agents pay this API?
Read-onlyIdempotent
Inspect

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.

NameRequiredDescriptionDefault
urlNoOr any URL on that host.
hostNoThe paid API's host, e.g. api.example.com.
verify_mcpVerify an MCP server works
Read-only
Inspect

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.

NameRequiredDescriptionDefault
urlYesThe MCP server's public https:// endpoint (Streamable HTTP), e.g. https://example.com/mcp.
callNoOptional sample call. Only made if the server marks the tool read-only (annotations.readOnlyHint).
expect_toolsNoTool names that must be listed.
verify_pageVerify a web page works
Read-only
Inspect

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.

NameRequiredDescriptionDefault
urlYesPublic https:// page to check, e.g. the page you just built or changed.
checksNoWhat must be true. 'loads' is always included.
viewportNoCheck as a desktop (1280 px) or phone (390 px) browser. Default desktop.
screenshotNoReturn a screenshot link (default true).
watch_listingWatch an MCP server's listings dailyInspect

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.

NameRequiredDescriptionDefault
npmNo
urlNoThe MCP server's public https:// endpoint to watch.
nameNo
pypiNo
webhookNoOptional public https:// URL: we POST a signed listing.changed event when something changes.
watch_idNoTo renew: an existing watch_id (adds 30 days).
registry_nameNo

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 12 tool updates
    • First observedcheck_payment_setup
    • First observedenrich_catalog
    • First observedhow_it_works
    • First observedlaunch_check
    • First observedlaunch_plan
    • First observedlaunch_plan_status
    • First observedlisting_status
    • First observedpublish_to_registry
    • First observedreliability_score
    • First observedverify_mcp
    • First observedverify_page
    • First observedwatch_listing

Related MCP Connectors

Related MCP Servers

  • A
    license
    A
    quality
    C
    maintenance
    Provides a JSON-RPC MCP server that exposes policy-governed agent tools, including paid tools, tool muxing, and OpenAPI-to-MCP conversion, enabling agents to discover, coordinate, and execute tasks within the ProtoOS ecosystem.
    5
    1
    Apache 2.0
  • A
    license
    Not graded
    quality
    B
    maintenance
    Runs the MCP initialize handshake and validates tools/list JSON schemas on any public MCP server, and inspects x402 payment endpoints. Ships as a stdio MCP server the agent calls directly, plus a CLI and a GitHub Action. Read-only, no API key needed.
    657 npm
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Unified crypto tool directory MCP server enabling AI agents to discover, evaluate, and install crypto tools across multiple sources with trust scoring and x402 payment support.
    1
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources