Tethered Trust
REMOTE · TETHEREDTRUST.COM
Compatibility checks for AI agents before they buy or install: verdicts, evidence, receipts.
Available components
Last scanned (14 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 23 Oct 2026.
Category E-commerce
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3699 tokens (~205/item across 18 items; 18 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.13.2 → 0.16.0 functional
- 15 Oct 26 71
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://tetheredtrust.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tetheredtrust.com | CN=WE1,O=Google Trust Services,C=US | 5 Oct 2026 | 3 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | e7c82f792058583b1371f731bb2e58d6 |
| SANs: tetheredtrust.com, www.tetheredtrust.com, *.www.tetheredtrust.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tetheredtrust.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| tetheredtrust.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tetheredtrust.com/mcp | Verified | 200 | |
| http (plaintext) | http://tetheredtrust.com/mcp | HTTPS enforced | 301 | https://tetheredtrust.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_batch Check many pairs ~47
Up to 25 independent compatibility checks in one call (e.g. ranking candidate products for one device). Each result has its own decision, evidence and receipt.
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
check_cart_before_checkout Check a cart before checkout ~249
Checks a cart at checkout. Takes the checkout session exactly as a commerce protocol returns it (a UCP checkout or an ACP CheckoutSession) or plain line items, plus what the customer already owns. Returns a decision per line item, safe_to_checkout, an action (proceed, resolve_conditions, do_not_checkout, ask_customer), questions, substitutions, a signed receipt, and a com.tetheredtrust.shopping.compatibility extension object to attach to the checkout.
| Name | Type | Req | Description |
|---|---|---|---|
| checkout | object | – | The checkout session as your commerce protocol returns it: a UCP checkout (line_items[].item.title) or an ACP CheckoutSession (line_items[].item.id). Or send line_items directly. |
| line_items | array | – | Generic cart: [{id, title | url | gtin | sku | text, quantity}]. Used when checkout isn't sent. |
| owned | array | – | What the customer already owns that these items must work with (model numbers, URLs or descriptions; objects may carry config like memory_modules). |
| products | object | – | ACP only: map of item id → {title | url | gtin} from your product feed, because ACP line items carry only ids. |
Structured output declared, but exposes no named fields.
No examples provided.
check_compatibility Check compatibility ~553
Will this exact part or accessory work with that exact device? Use before recommending or buying. Covers anything that has to fit, plug in, mount, run on or charge with something someone owns. Verified catalog (specs checked against cited manufacturer sources): computers & consoles (RAM, M.2 SSDs, USB-C chargers), phones/tablets/watches (USB-C PD, MagSafe, Qi2, watch bands), cameras (lens mounts, adapters, batteries, memory cards), cordless power tools (battery platforms), printers (ink, toner, drums), appliances (refrigerator water and air filters, installation fit), vacuums (bags, filters, batteries, robot-vacuum parts), air quality (purifier filters, HVAC media, humidifier pads), e-bikes (batteries and chargers by drive system), smart home (Matter, Thread, Zigbee, hubs, bulb bases), PC building (CPU sockets, cooler mounts, memory, clearances, power), cars & EV charging (tire sizes by trim, NACS/J1772/CCS1 and approved adapters, home chargers; a starter set of models) and TVs, consoles & streaming (VESA mounts, weight and screen size, console generations, app platforms). Products outside the catalog in any category are read by AI in terms of the same standards and returned as unverified. Returns a decision (supported / conditional / incompatible / insufficient_evidence), the rules checked, caveats, required accessories, the questions to ask when it can't decide, evidence links and a signed receipt. When the text matches several models it returns each candidate's answer.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate | string | yes | What they want to buy: a model/part number or key specs, e.g. 'Crucial CT16G4SFRA32A', '1TB M.2 2230 NVMe', 'DCB205', 'HP 962XL', 'Canon RF 24-105mm f/4L', 'Eve Energy'. |
| candidate_id | string | – | Optional: an exact product id instead of candidate text. |
| detail | string | – | Optional extra identifiers: machine type, revision, year, region, serial range. |
| existing | string | yes | What the person already has, ideally with the exact model number, e.g. 'Lenovo ThinkPad T480', 'Sony A7 IV', 'DeWalt DCD800', 'HP OfficeJet Pro 9015e', 'iPhone 16 Pro', 'HomePod mini'. |
| existing_id | string | – | Optional: an exact product id (from resolve_product, suggestions or a candidates list) instead of existing text. |
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | object | – | Present when the text matched several models: each option with its own verdict. |
| caveats | array | – | – |
| check_id | string | yes | – |
| checks | array | – | – |
| conditions | array | – | What must be true for a conditional answer (accessory, dependency). |
| confidence | number | yes | Evidence score from fixed rules (source tier, rule strength). Not a calibrated probability: act on decision, conditions and questions. |
| constraints | array | – | – |
| decision | string | yes | supported | conditional | incompatible | insufficient_evidence. Act on this, not on confidence alone. |
| decision_help | string | – | – |
| evidence | array | – | – |
| fit | boolean|null | – | – |
| missing | array | – | – |
| next_step | string | – | – |
| notice | string | – | – |
| questions | array | – | Exactly what to ask, measure or look up next. blocking=true means no decision until answered. |
| receipt | object|null | – | Signed receipt (EdDSA JWS) proving Tethered Trust issued this verdict unaltered. Not a guarantee the verdict is correct. |
| required_accessories | array | – | – |
| requirements | object | – | – |
| summary | string | yes | – |
| terms | string | – | – |
| valid_until | string | – | When this answer should be re-checked (based on how fresh its sources are). |
| verdict | string | yes | – |
| verified | boolean | – | True only when every spec came from a manufacturer source with a recorded check date. |
No examples provided.
check_fit Check physical fit ~171
Will this appliance physically fit this space? Compares dimensions plus typical installation clearances and required connections (power, water, gas).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| has | string | – | Connections available at the location. |
| needs | string | – | Connections the product needs, e.g. '120V, water line' or '240V'. |
| opening | object | yes | Width, height and depth of the space it goes into. Any subset is accepted; missing axes come back as 'missing'. |
| product | string | – | What's being installed, e.g. '36-inch French-door refrigerator'. Used to pick typical clearances. |
| product_dimensions | object | – | Width, height and depth of the product (from its spec sheet). Any subset is accepted; missing axes come back as 'missing'. |
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | object | – | Present when the text matched several models: each option with its own verdict. |
| caveats | array | – | – |
| check_id | string | yes | – |
| checks | array | – | – |
| conditions | array | – | What must be true for a conditional answer (accessory, dependency). |
| confidence | number | yes | Evidence score from fixed rules (source tier, rule strength). Not a calibrated probability: act on decision, conditions and questions. |
| constraints | array | – | – |
| decision | string | yes | supported | conditional | incompatible | insufficient_evidence. Act on this, not on confidence alone. |
| decision_help | string | – | – |
| evidence | array | – | – |
| fit | boolean|null | – | – |
| missing | array | – | – |
| next_step | string | – | – |
| notice | string | – | – |
| questions | array | – | Exactly what to ask, measure or look up next. blocking=true means no decision until answered. |
| receipt | object|null | – | Signed receipt (EdDSA JWS) proving Tethered Trust issued this verdict unaltered. Not a guarantee the verdict is correct. |
| required_accessories | array | – | – |
| requirements | object | – | – |
| summary | string | yes | – |
| terms | string | – | – |
| valid_until | string | – | When this answer should be re-checked (based on how fresh its sources are). |
| verdict | string | yes | – |
| verified | boolean | – | True only when every spec came from a manufacturer source with a recorded check date. |
No examples provided.
enrich_catalog Enrich a product catalog ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| research | boolean | – | Default true: research up to 10 items per call that aren't in our catalog (from the manufacturer's page). |
Structured output declared, but exposes no named fields.
No examples provided.
find_parts Find parts that fit ~167
Which parts and accessories fit this model? OEM parts first, then verified alternatives: e.g. a refrigerator's water filter, a printer's cartridges, a camera's lenses and batteries, a tool's batteries, or the RAM, SSDs and chargers that fit a computer.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | yes | Model number of the device, tool, camera, printer or appliance, e.g. 'GFE28GYNFS', 'ThinkPad T480', 'Canon EOS R6 Mark II', 'Milwaukee 2904-20', 'Brother HL-L2350DW'. |
| part_type | string | – | Optional filter, e.g. 'water filter', 'memory', 'ssd', 'charger', 'battery', 'lens', 'ink', 'toner', 'band'. |
| Name | Type | Req | Description |
|---|---|---|---|
| check_id | string | yes | – |
| found | boolean | yes | – |
| message | string | yes | – |
| model | – | – | – |
| notice | string | – | – |
| parts | array | yes | – |
| terms | string | – | – |
| total | number | – | – |
No examples provided.
fix_purchase_plan Fix a purchase plan ~167
When a plan comes back incompatible or conditional: the smallest set of changes that makes it work (swap a part for a verified one that fits everything else, add a missing cooler, hub or adapter, trim quantities that exceed slots), re-validated, with the reason for each change. Fewest changes and verified products first; no prices.
| Name | Type | Req | Description |
|---|---|---|---|
| goal | string | – | Optional: what the person is trying to do, e.g. 'upgrade this laptop to 32 GB'. Echoed back; requirements are derived from the devices. |
| purchase | array | yes | Everything being considered for purchase: parts, accessories or new devices, with quantities. |
| setup | array | – | What the person already owns (devices, appliances, tools, hubs) with exact model numbers, plus current configuration. |
Structured output declared, but exposes no named fields.
No examples provided.
how_it_works How Tethered Trust works ~31
What Tethered Trust is, what it covers, where its data comes from, pricing and terms.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
identify_from_photo Read a model number from a photo ~100
Read the brand, model and part numbers from a photo of a label or nameplate and match them to products. Matches are returned as candidates, with what was read. The photo isn't stored.
| Name | Type | Req | Description |
|---|---|---|---|
| hint | string | – | Optional context, e.g. 'refrigerator label inside the door'. |
| image | string | yes | A photo of the label or nameplate as a data URL (data:image/jpeg;base64,...), under 4 MB. |
Structured output declared, but exposes no named fields.
No examples provided.
identify_product Identify any product ~225
Identify a product from a URL, model number, SKU, ASIN, UPC/EAN or description, and get its compatibility profile: the standards it takes and provides (mounts, sockets, connectors, platforms, part numbers, sizes), numeric limits (OS version, watts, weight, screen size), evidence and freshness. Products not in our reviewed catalog are researched on demand from the manufacturer's page and returned with status read_from_manufacturer_page (unreviewed) or unconfirmed (not enough to decide on). Use first when the product could be anything.
| Name | Type | Req | Description |
|---|---|---|---|
| product | string | yes | Anything that identifies the product: a manufacturer or retailer URL, a model number, SKU, ASIN, UPC/EAN, a vehicle VIN, or a listing title / description. |
| research | boolean | – | Default true. Set false to look only in the reviewed catalog (no on-demand research). |
| role | string | – | Optional: is this something the person already owns, or something being considered? Helps when a product is both (a phone owns cases; a car mount holds phones). |
Structured output declared, but exposes no named fields.
No examples provided.
list_coverage List coverage ~323
Which product categories and models are in the compatibility graph, with counts. Pass a category to list its models. Covers anything that has to fit, plug in, mount, run on or charge with something someone owns. Verified catalog (specs checked against cited manufacturer sources): computers & consoles (RAM, M.2 SSDs, USB-C chargers), phones/tablets/watches (USB-C PD, MagSafe, Qi2, watch bands), cameras (lens mounts, adapters, batteries, memory cards), cordless power tools (battery platforms), printers (ink, toner, drums), appliances (refrigerator water and air filters, installation fit), vacuums (bags, filters, batteries, robot-vacuum parts), air quality (purifier filters, HVAC media, humidifier pads), e-bikes (batteries and chargers by drive system), smart home (Matter, Thread, Zigbee, hubs, bulb bases), PC building (CPU sockets, cooler mounts, memory, clearances, power), cars & EV charging (tire sizes by trim, NACS/J1772/CCS1 and approved adapters, home chargers; a starter set of models) and TVs, consoles & streaming (VESA mounts, weight and screen size, console generations, app platforms). Products outside the catalog in any category are read by AI in terms of the same standards and returned as unverified.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional: one category id from a previous list_coverage call (e.g. 'cameras') to list every model in it. |
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | yes | – |
| models | array | – | – |
| totals | object | yes | – |
No examples provided.
list_standards List the standards vocabulary ~51
Every compatibility standard family (with reviewed values), the open formats used for new values, and the numeric limit keys. How Tethered Trust represents physical connections, dimensional fit, vehicles, software and services.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
plan_upgrade Plan an upgrade ~136
What can be upgraded on this device and with what: memory (type, slots, maximum), storage (M.2 slots, lengths, PCIe generation), power, CPU and cooling for motherboards, graphics card and cooler clearance for PC cases, plus the parts in our graph that fit (verified first) and the manufacturer's notes.
| Name | Type | Req | Description |
|---|---|---|---|
| goal | string | – | Optional: what the person wants, e.g. 'more memory for video editing'. |
| id | string | – | Or its product id. |
| model | string | – | The device's exact model number or name (laptop, motherboard, case, camera, tool...). |
Structured output declared, but exposes no named fields.
No examples provided.
recheck_plan Recheck a saved plan ~54
Re-run a saved purchase plan against today's data before ordering, and see what changed since it was issued: decisions, product records, or receipt status.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_id | string | yes | The plan_id from validate_purchase_plan. |
Structured output declared, but exposes no named fields.
No examples provided.
report_outcome Report what happened ~160
After a purchase, report whether it actually fit. Free, safe to call, and only the first report per check counts. Reports are weighted by level: self_reported (website), agent_reported (anonymous API/MCP), partner_reported (API key holders) and order_confirmed (order evidence we've confirmed). Only the last two can raise future confidence.
| Name | Type | Req | Description |
|---|---|---|---|
| check_id | string | yes | The check_id returned by check_compatibility, find_parts or check_fit. |
| evidence | object | – | Optional order details we can confirm later (raises the report to 'order_confirmed' once reviewed). Order references only; payment and personal details aren't accepted. |
| note | string | – | What happened, briefly. |
| outcome | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| evidence_received | boolean | – | – |
| level | string|null | – | – |
| message | string | yes | – |
| recorded | boolean | yes | – |
No examples provided.
resolve_product Look up a product ~85
Look up one product in the Tethered Trust graph by name or model number and get its structured specs, what it accepts (mounts, battery platforms, cartridges, protocols) and what it fits. If the text could mean several models, returns them all as candidates (ambiguous: true) with ambiguous: true.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Product name or model number. |
| Name | Type | Req | Description |
|---|---|---|---|
| ambiguous | boolean | – | – |
| candidates | array | – | – |
| found | boolean | yes | – |
| message | string | – | – |
| product | object | – | – |
| read_from_text | – | – | – |
No examples provided.
validate_purchase_plan Validate a purchase plan ~446
Check a whole purchase before recommending or ordering it: the setup the person owns (with current configuration) plus everything in the cart. Returns one decision (supported / conditional / incompatible / insufficient_evidence), a result per part, configuration limits across the plan (memory slots and capacity, M.2 slots), adapters or hubs still needed, substitutions for parts that won't work, the exact questions blocking a decision, evidence, and a signed receipt. Covers anything that has to fit, plug in, mount, run on or charge with something someone owns. Verified catalog (specs checked against cited manufacturer sources): computers & consoles (RAM, M.2 SSDs, USB-C chargers), phones/tablets/watches (USB-C PD, MagSafe, Qi2, watch bands), cameras (lens mounts, adapters, batteries, memory cards), cordless power tools (battery platforms), printers (ink, toner, drums), appliances (refrigerator water and air filters, installation fit), vacuums (bags, filters, batteries, robot-vacuum parts), air quality (purifier filters, HVAC media, humidifier pads), e-bikes (batteries and chargers by drive system), smart home (Matter, Thread, Zigbee, hubs, bulb bases), PC building (CPU sockets, cooler mounts, memory, clearances, power), cars & EV charging (tire sizes by trim, NACS/J1772/CCS1 and approved adapters, home chargers; a starter set of models) and TVs, consoles & streaming (VESA mounts, weight and screen size, console generations, app platforms). Products outside the catalog in any category are read by AI in terms of the same standards and returned as unverified.
| Name | Type | Req | Description |
|---|---|---|---|
| goal | string | – | Optional: what the person is trying to do, e.g. 'upgrade this laptop to 32 GB'. Echoed back; requirements are derived from the devices. |
| purchase | array | yes | Everything being considered for purchase: parts, accessories or new devices, with quantities. |
| setup | array | – | What the person already owns (devices, appliances, tools, hubs) with exact model numbers, plus current configuration. |
| Name | Type | Req | Description |
|---|---|---|---|
| confidence | number | – | – |
| decision | string | yes | – |
| evidence | array | – | – |
| items | array | – | – |
| next_step | string | – | – |
| plan_id | string | yes | – |
| questions | array | – | – |
| receipt | object|null | – | – |
| required_accessories | array | – | – |
| requirements | array | – | – |
| results | array | yes | – |
| substitutions | array | – | – |
| summary | string | yes | – |
| system_checks | array | – | – |
| valid_until | string | – | – |
No examples provided.
verify_receipt Verify a receipt ~96
Check a Tethered Trust receipt: is the signature ours, is it still within valid_until, and have the records behind it changed since? A valid receipt proves what we said and when; it doesn't guarantee the verdict was right.
| Name | Type | Req | Description |
|---|---|---|---|
| jws | string | – | Or the full signed receipt string, if someone handed it to you. |
| receipt_id | string | – | The receipt id (rcpt_...) from a check. |
| Name | Type | Req | Description |
|---|---|---|---|
| changed_subjects | array | – | – |
| claim | object | – | – |
| disclaimer | string | – | – |
| explain | string | – | – |
| issued_at | string | – | – |
| issued_by_tethered_trust | boolean | – | – |
| receipt_id | string | – | – |
| signature_valid | boolean | yes | – |
| status | string | yes | – |
| valid_until | string | – | – |
No examples provided.
How do I install the Tethered Trust MCP server?
Tethered Trust is a hosted endpoint at https://tetheredtrust.com/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.
remote · tetheredtrust.com
claude mcp add --transport http com-tetheredtrust-tethered-trust 'https://tetheredtrust.com/mcp'
What is the Tethered Trust MCP server?
Tethered Trust is an MCP server listed in the public MCP registry as com.tetheredtrust/tethered-trust. Compatibility checks for AI agents before they buy or install: verdicts, evidence, receipts. This page covers its hosted endpoint (https://tetheredtrust.com/mcp).
Is the Tethered Trust MCP server safe to use?
Tethered Trust scores 74 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 Tethered Trust MCP server expose?
Tethered Trust exposes 18 tools: how_it_works, list_coverage, check_cart_before_checkout, enrich_catalog, identify_product, and 13 more. Their descriptions and schemas cost roughly 3,175 tokens of context every time the server is loaded.
Does the Tethered Trust MCP server require authentication?
No. We connected to Tethered Trust without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Tethered Trust MCP server still maintained?
Tethered Trust is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.