Ampdat Control
REMOTE · CONTROL.AMPDAT.COM
Who controls a DeFi vault (Morpho today), Safe or stablecoin, and what is about to change.
Available components
Last scanned (13 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Crypto and Web3
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 Security74
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1352 tokens (~270/item across 5 items; 5 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 69% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +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.
- 20 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 241 → 270 ▼ functional
- 18 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 17 Nov 26 68
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 21 Nov 2026 · Probed https://control.ampdat.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=control.ampdat.com | CN=WR3,O=Google Trust Services,C=US | 7 Nov 2026 | 5 Feb 2027 | RSA 2048 | SHA256-RSA | 342ac0ed8cd1734212be89fbf4a69e1c |
| SANs: control.ampdat.com | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of control.ampdat.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| ampdat.com. | No DS | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://control.ampdat.com/mcp | Verified | 200 | |
| http (plaintext) | http://control.ampdat.com/mcp | HTTPS enforced | 302 | https://control.ampdat.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 →
get_change_records Change history and feed (paid) ~241
Past and recent changes as records, for monitoring a position or auditing a contract's history: the change history as record/v1 records, oldest first: what changed, from what to what, who acted, who may execute or revoke it, when it takes effect, and the transaction and log each rests on. With `address`, one contract's history; without, the feed across every covered contract (filter with `since`, a block number). Paged: pass the previous result's next_cursor. Paid per call over x402; a call without a payment returns the price and where to buy, and charges nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Optional: only this contract's records. |
| cursor | string | – | – |
| family | string | – | Feed only: a family id from get_coverage, e.g. metamorpho-v1.1. |
| kind | – | – | – |
| limit | integer | – | – |
| observed_status | – | – | A record's status as first observed; a record never changes, so what is pending now is get_control_state's `pending`. |
| since | integer | – | First Ethereum block to include (default 0). |
No output schema declared.
No examples provided.
get_control_evidence The evidence-backed control answer (paid) ~250
The machine-readable, evidence-backed answer for one covered contract (the subject/v1 envelope): the full control graph (each Safe's signers, threshold, modules and guard, EIP-7702 delegates, and what is still unresolved), the complete state (every market, cap and queue), every pending change as a record with the transaction and log it rests on, the 20 most recent changes, and the value at stake. Use it when the user needs to verify or audit, not just read: the whole chain behind a role holder in one answer, what a pending change rests on, or the exact caps. Paid per call over x402; a call without a payment returns the price and where to buy, and charges nothing. get_control_state is the free summary.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The contract's address on Ethereum mainnet (0x and 40 hex digits), e.g. a Morpho vault's, a Safe's or a stablecoin's. Not a name: use search_covered_contracts to find an address. |
| sections | array | – | Optional: only these parts of the envelope (default all). The whole answer can exceed 50 KB. |
No output schema declared.
No examples provided.
get_control_state Who controls this contract, and what is pending ~263
Who controls a covered contract right now: who holds each role and what that holder is (a single key, a Safe and its threshold, a DAO, a known contract); what each role can change and how much notice (timelock) each change gives; and every change already queued, when it can take effect and who can revoke it. For a Morpho vault, before a deposit or while holding: the owner, curator, guardian or sentinels, and allocators. For a stablecoin: who can mint, burn, pause, freeze, upgrade the contract or appoint those roles. For a Safe: its signers' threshold, modules and guards, and the vault roles it holds (holds_roles_on); a Safe changes in one transaction, so nothing in it is pending. Deterministic facts from the chain at a stated block; a title search, not a rating, so it returns no safety score. An address that is not covered returns covered: false.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The contract's address on Ethereum mainnet (0x and 40 hex digits), e.g. a Morpho vault's, a Safe's or a stablecoin's. Not a name: use search_covered_contracts to find an address. |
No output schema declared.
No examples provided.
get_coverage What Ampdat Control covers ~142
What this server can answer about: which contract families on which chain (today, on Ethereum mainnet: every Morpho vault, MetaMorpho v1.0 and v1.1 and Morpho Vaults V2; the Safes that hold those vaults' roles; and the contracts of six stablecoins, USDC, USDT, USDS, DAI, PYUSD and USD1), how many contracts, and the block the data is at. Call it once to learn the scope, or with `address` to check whether one address is covered before relying on an answer.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Optional: check this address. |
No output schema declared.
No examples provided.
search_covered_contracts Find a covered contract by name ~131
Find a covered contract's address from words the user gave: its name (e.g. 'Steakhouse USDC'), its asset symbol (e.g. 'WETH') or part of its address. Returns up to `limit` matches with address, name, asset and family. Use it when the user names a vault or a coin instead of giving an address, then call get_control_state with the address.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | Words that must all appear in the contract's name, asset symbol, family or address. Case does not matter. |
No output schema declared.
No examples provided.
How do I install the Ampdat Control MCP server?
Ampdat Control is a hosted endpoint at https://control.ampdat.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 · control.ampdat.com
claude mcp add --transport http com-ampdat-control 'https://control.ampdat.com/mcp'
What is the Ampdat Control MCP server?
Ampdat Control is an MCP server listed in the public MCP registry as com.ampdat/control. Who controls a DeFi vault (Morpho today), Safe or stablecoin, and what is about to change. This page covers its hosted endpoint (https://control.ampdat.com/mcp).
Is the Ampdat Control MCP server safe to use?
Ampdat Control scores 70 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 Ampdat Control MCP server expose?
Ampdat Control exposes 5 tools: get_coverage, search_covered_contracts, get_control_state, get_control_evidence, get_change_records. Their descriptions and schemas cost roughly 1,027 tokens of context every time the server is loaded.
Does the Ampdat Control MCP server require authentication?
No. We connected to Ampdat Control without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Ampdat Control MCP server still maintained?
Ampdat Control is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Ampdat Control MCP server?
VerifyMCP ran 13 checks on Ampdat Control, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.