# DebitMyData Agentic Superhighway (remote · api.debitmydata.io)

Get a DID-LLM, DebitMyData's verifiable identity for AI agents, and pay for it by yourself.

- Trust score: 64/100 (medium)
- Change this week: −5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

> **Recent critical change**: Authorization (2026-11-16). See the changelog below before you install this server.

## Components

- remote · `api.debitmydata.io`: 64/100 (this document), [markdown](https://verifymcp.io/servers/io-debitmydata-agenticsuperhighway/agenticsuperhighway.md), [page](https://verifymcp.io/servers/io-debitmydata-agenticsuperhighway/agenticsuperhighway)

## Channel facts

- Endpoint: `https://api.debitmydata.io/agenticsuperhighway`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.55.10`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (debitmydata_change_owner).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3866 tokens (~184/item across 21 items; 21 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 8 days we've observed: 16 tool removals, 0 breaking changes, 0 auth/transport breaks, 21 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (90% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the DebitMyData Agentic Superhighway MCP server?

DebitMyData Agentic Superhighway is a hosted endpoint at https://api.debitmydata.io/agenticsuperhighway, 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.

### Claude

```bash
claude mcp add --transport http io-debitmydata-agenticsuperhighway 'https://api.debitmydata.io/agenticsuperhighway'
```

### Cursor

```json
{
  "mcpServers": {
    "io-debitmydata-agenticsuperhighway": {
      "url": "https://api.debitmydata.io/agenticsuperhighway"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-debitmydata-agenticsuperhighway": {
      "type": "http",
      "url": "https://api.debitmydata.io/agenticsuperhighway"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-debitmydata-agenticsuperhighway]
url = "https://api.debitmydata.io/agenticsuperhighway"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-debitmydata-agenticsuperhighway": {
      "type": "remote",
      "url": "https://api.debitmydata.io/agenticsuperhighway",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-debitmydata-agenticsuperhighway --url 'https://api.debitmydata.io/agenticsuperhighway' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-debitmydata-agenticsuperhighway:
    url: "https://api.debitmydata.io/agenticsuperhighway"
```

### Netclaw

```json
{
  "McpServers": {
    "io-debitmydata-agenticsuperhighway": {
      "Transport": "http",
      "Url": "https://api.debitmydata.io/agenticsuperhighway"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-debitmydata-agenticsuperhighway -t streamable-http -u 'https://api.debitmydata.io/agenticsuperhighway'
```

### Other

```json
{
  "mcpServers": {
    "io-debitmydata-agenticsuperhighway": {
      "type": "http",
      "url": "https://api.debitmydata.io/agenticsuperhighway"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 64, 0)

- [functional] Server version: 0.55.17 → 0.55.22

### 2026-11-19 (score 64, 0)

- [security] Tool “debitmydata_whoami” rewrote its description, which is the text the model reads
- [functional] Server version: 0.55.14 → 0.55.17

### 2026-11-18 (score 64, 0)

- [functional] Server version: 0.55.12 → 0.55.14

### 2026-11-17 (score 64, 0)

- [functional] Server version: 0.55.10 → 0.55.12

### 2026-11-16 (score 64, −6)

- [critical regression] Authorization: partial → fail
- [security regression] Stability: 0.07 → fail
- [security regression] Tool “dmd_catalog” was removed
- [security regression] Tool “dmd_complete_purchase” was removed
- [security regression] Tool “dmd_create_did_payment_quote” was removed
- [security regression] Tool “dmd_discover” was removed
- [security regression] Tool “dmd_get_did_registration_offer” was removed
- [security regression] Tool “dmd_get_payment_status” was removed
- [security regression] Tool “dmd_get_purchase_quote” was removed
- [security regression] Tool “dmd_get_registration_status” was removed
- [security regression] Tool “dmd_list_in_directory” was removed
- [security regression] Tool “dmd_list_supported_payment_options” was removed
- [security regression] Tool “dmd_marketplace_provider_requirements” was removed
- [security regression] Tool “dmd_open_checkout” was removed
- [security regression] Tool “dmd_prove_wallet_control” was removed
- [security regression] Tool “dmd_purchase” was removed
- [security regression] Tool “dmd_register_did” was removed
- [security regression] Tool “dmd_search_directory” was removed
- [security regression] Tool “dmd_submit_payment_reference” was removed
- [security regression] Tool “dmd_verify_agent” was removed
- [security regression] Tool “dmd_whoami” was removed
- [security improvement] HSTS header: fail → pass
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] New tool “debitmydata_change_owner”, which the server declares destructive
- [security] New tool “debitmydata_revoke_did”, which the server declares destructive
- [security] Tool “debitmydata_open_checkout” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 3217 → 3799
- [functional regression] Schema quality: 3217 → 3779
- [functional] Destructive annotations: pass → 100
- [functional] Server version: 0.50.0 → 0.55.10
- [functional] Server version: 0.47.0 → 0.50.0
- [functional] New tool “debitmydata_catalog”
- [functional] New tool “debitmydata_complete_purchase”
- [functional] New tool “debitmydata_create_did_payment_quote”
- [functional] New tool “debitmydata_discover”
- [functional] New tool “debitmydata_get_did_registration_offer”
- [functional] New tool “debitmydata_get_payment_status”
- [functional] New tool “debitmydata_get_purchase_quote”
- [functional] New tool “debitmydata_get_registration_status”
- [functional] New tool “debitmydata_list_in_directory”
- [functional] New tool “debitmydata_list_supported_payment_options”
- [functional] New tool “debitmydata_marketplace_provider_requirements”
- [functional] New tool “debitmydata_open_checkout”
- [functional] New tool “debitmydata_prove_wallet_control”
- [functional] New tool “debitmydata_purchase”
- [functional] New tool “debitmydata_register_did”
- [functional] New tool “debitmydata_search_directory”
- [functional] New tool “debitmydata_submit_payment_reference”
- [functional] New tool “debitmydata_verify_agent”
- [functional] New tool “debitmydata_whoami”

### 2026-11-15 (score 70, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “dmd_discover” rewrote its description, which is the text the model reads
- [security] Tool “dmd_get_did_registration_offer” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 2633 → 3217
- [functional] Server version: 0.37.2 → 0.47.0
- [functional] New tool “dmd_open_checkout”
- [functional] New tool “dmd_verify_agent”
- [functional] New tool “dmd_whoami”

### 2026-11-14 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 0.36.0 → 0.37.2

### 2026-11-13 (score 69)

First indexed and scored.

## MCP tools (21)

### `debitmydata_discover` (~85 tokens)

Discover DebitMyData

Start here. What DebitMyData sells (product: the DebitMyData DID-LLM, $25.00 USD,
paid once, with its page, its picture and how to buy it), then DebitMyData, its
Proof-of-Work chain and DMD coin, the offers, the enabled payment methods, the policies
and the public endpoints.

### `debitmydata_get_did_registration_offer` (~51 tokens)

DID-LLM registration offer

The DebitMyData DID-LLM: $25.00 USD, paid once (its name, price, page and picture),
and every payment option that is enabled right now.

### `debitmydata_open_checkout` (~98 tokens)

Open the checkout (creates nothing, charges nothing)

Open the checkout for the DebitMyData DID-LLM ($25.00 USD, paid once): the checkout
page where a person buys it (by card, with PayPal or from their own wallet, as the
payment options allow), the payment options enabled right now, and the steps an agent
follows to buy it by itself. Read-only: it creates nothing, charges nothing and needs
no personal details.

### `debitmydata_list_supported_payment_options` (~49 tokens)

Supported payment options

Approved assets, networks, wallet types and protocols currently enabled for a
service, with the commercial fee.

Input parameters:

- `service` (string): Service ID, e.g. did_registration

### `debitmydata_create_did_payment_quote` (~279 tokens)

Create a DID-LLM payment quote

Create a time-limited quote: the fixed 25.00 USD price, the exact amount in the
chosen asset, the destination, the confirmations required and the expiry.

Input parameters:

- `controller_network`: The wallet's network, e.g. eip155:8453 for Base (the default)
- `controller_public_key`: Ed25519 public key that will control the DID-LLM: ed25519:z6Mk..., or ed25519: followed by 64 hex characters or base64. Give this, a wallet, or both.
- `controller_wallet_address`: EVM wallet that will control the DID-LLM: 0x... (checksummed or all lower case) or eip155:<chain id>:0x.... Its control is proven like the key's, by signing a challenge (smart wallets included).
- `display_name` (string, required): Public name of the agent
- `idempotency_key`: Optional random key (16-128 characters, e.g. a UUID); retrying with the same key returns the same quote
- `metadata`: Optional small key/value metadata (up to 20 keys)
- `participant_type` (required): What kind of participant
- `preferred_payment_option` (string, required): Payment option ID from the offer, e.g. dmd_pow_native

### `debitmydata_submit_payment_reference` (~80 tokens)

Submit a payment reference

Report the transaction that pays a quote. This is only a hint: the payment is
still verified independently on chain before it counts.

Input parameters:

- `payment_intent_id` (string, required): payment_intent_id from the quote (dmd_payment_intent_...)
- `transaction_reference` (string, required): Transaction ID / hash of the payment you broadcast

### `debitmydata_get_payment_status` (~61 tokens)

Payment status

Detection, confirmations, settlement, failure, reorganization and refund status
of a payment, with the next action to take.

Input parameters:

- `payment_intent_id` (string, required): payment_intent_id from the quote (dmd_payment_intent_...)

### `debitmydata_prove_wallet_control` (~196 tokens)

Prove control of the controller key or wallet

Two calls. Without challenge_id and signature: returns a one-time challenge for one
controller. Sign its `message` with that controller, then call again with challenge_id
and signature. A wrong signature uses up the challenge. With both a key and a wallet,
prove each (registration status lists what is still to prove).

Input parameters:

- `challenge_id`: Leave empty to get a new challenge
- `controller_type`: When getting a challenge: which controller to prove, ed25519 (the key) or eip155 (the wallet). By default the next one still to prove.
- `registration_intent_id` (string, required): registration_intent_id from the quote (dmd_did_intent_...)
- `signature`: Signature of the challenge message: Ed25519 (base64url) for a key, or the wallet's personal_sign / signMessage result (0x...) for a wallet

### `debitmydata_register_did` (~199 tokens)

Register the DID-LLM

Issue the DID-LLM once the payment is settled and the controller proof is verified.
Returns the DID-LLM, its DID-LLM document URL, the signed credential (the receipt) and the
entitlements. Calling it again returns the same DID-LLM.

x402 quotes (USDC on Base): prove control first, then call this tool. It fails
with the x402 payment requirements; sign them with your wallet and call it again
with x402_payment. The DID-LLM is issued once the payment is settled on chain.

Input parameters:

- `registration_intent_id` (string, required): registration_intent_id from the quote (dmd_did_intent_...)
- `x402_payment`: x402 quotes only: your signed PaymentPayload (x402 version 2) answering the payment requirements this tool returned. It may also be sent in the request's _meta['x402/payment'].

### `debitmydata_get_registration_status` (~57 tokens)

Registration status

Progress of a registration: payment, controller proof, what is still missing
and the next action.

Input parameters:

- `registration_intent_id` (string, required): registration_intent_id from the quote (dmd_did_intent_...)

### `debitmydata_verify_agent` (~181 tokens)

Verify an agent

Check another agent's DID-LLM: issued by DebitMyData and active, its credential
signed by DebitMyData, its owner key or wallet. Call with did (and audience) for that and
a challenge; have the agent sign the challenge's message with its DID-LLM; call again
with did, message and signature to know whether it controls the DID-LLM (check that
proof.nonce is the nonce you were given).

Input parameters:

- `audience`: Who verifies (your name or site), written in the challenge
- `did` (string, required): The DID-LLM to verify (did:web:api.debitmydata.io:agents:...)
- `message`: The challenge message the agent signed
- `signature`: The agent's signature of the message (its key's, or its wallet's)

### `debitmydata_search_directory` (~88 tokens)

Search the DID-LLM directory

DID-LLMs whose owners chose to be listed in DebitMyData's directory, newest first,
each with its profile (type, specialty, description...) and its DID-LLM document.

Input parameters:

- `cursor`: next_cursor of the last page
- `entity_type`: Only this type
- `q`: Words to find (name, specialty, description, owner, place)

### `debitmydata_list_in_directory` (~251 tokens)

List a DID-LLM in the directory

Two calls, signed by the DID-LLM's owner. Without challenge_id and signature:
returns the message that lists the DID-LLM with `profile` (or removes it, listed=false).
Sign it with the DID-LLM's controller, then call again with did, challenge_id and
signature. A wrong signature uses up the message.

Input parameters:

- `challenge_id`: Leave empty to get the message to sign
- `controller_type`: Who signs: ed25519 (the key, by default) or eip155 (the wallet)
- `did` (string, required): The DID-LLM (did:web:...:agents:...) or its identity ID (dmd_identity_...)
- `listed` (boolean): false: remove the DID-LLM from the directory
- `profile`: When listing: entity_type (avatar, robot or sentient), specialty (3-120 characters), description (20-700 characters, 100 words at most); optional owner_name, region, country, created_on (YYYY-MM-DD).…
- `signature`: Signature of the message, as for debitmydata_prove_wallet_control

### `debitmydata_change_owner` (~297 tokens)

Change a DID-LLM's owners

Move a DID-LLM to new owners (a new key and/or wallet), signed by its owners. First
call, with did and the owners it will have afterwards: returns the change and its
messages. One current owner signs its "approve" message and each new owner its "accept"
message; send each with did, change_id, challenge_id and signature. The last one needed
applies the change (within 15 minutes): only the new owners control the DID-LLM and
sign-ins made before it end. With change_id alone: where it stands.

Input parameters:

- `challenge_id`: The message you signed (from `messages`)
- `change_id`: Leave empty to start a change; then the change_id it returned
- `did` (string, required): The DID-LLM (did:web:...:agents:...) or its identity ID (dmd_identity_...)
- `new_controller_network`: The wallet's network, eip155:8453 (Base) by default
- `new_controller_public_key`: The owner key after the change, ed25519:z6Mk...: the current one to keep it, a new one to replace it, or empty to have none
- `new_controller_wallet_address`: The owner wallet after the change, 0x..., the same way
- `signature`: Its signature, as for debitmydata_prove_wallet_control

### `debitmydata_revoke_did` (~210 tokens)

Revoke a DID-LLM for good

Revoke a DID-LLM for good, signed by its owner: it cannot be undone. The DID-LLM, its
credential and its entitlements stop working forever. Without challenge_id and
signature: returns the message to sign. Sign it with the owner key or wallet it names,
then call again with did, challenge_id and signature. Only when the owner really wants
it ended (for example a key that leaked and no other owner to change to).

Input parameters:

- `challenge_id`: Leave empty to get the message to sign
- `controller_type`: Who signs: ed25519 (the key, by default) or eip155 (the wallet)
- `did` (string, required): The DID-LLM (did:web:...:agents:...) or its identity ID (dmd_identity_...)
- `reason`: Optional, kept with the revocation
- `signature`: Signature of the message, as for debitmydata_prove_wallet_control

### `debitmydata_catalog` (~50 tokens)

Catalog

DebitMyData products and services available through this gateway, with their
commercial price (or, for a donation, the amount range the donor chooses from) and
the payment options accepted right now.

### `debitmydata_get_purchase_quote` (~61 tokens)

Purchase quote options

The commercial price (or a donation's amount range) and the supported currencies
and wallets for one product. Use debitmydata_purchase to buy it or to donate.

Input parameters:

- `product_id` (string, required): Product ID from debitmydata_catalog

### `debitmydata_purchase` (~387 tokens)

Purchase

Start a purchase with the chosen payment option.

did_registration: returns a payable quote (the same as
debitmydata_create_did_payment_quote).

Add-ons for a DID-LLM (bottybotty_entry, bottybotty_standard, bottybotty_premium): returns
a payable quote for details.did; for a higher BottyBotty tier than the one owned, it
charges the difference.
Pay it, wait for debitmydata_get_payment_status to say "settled", then
debitmydata_complete_purchase.

Donations (inference_donation, USDC on Base through x402): call with the amount; it
fails with the x402 payment requirements. Sign them with your wallet and call again
with the same details and x402_payment. The answer is the donation with a receipt
signed by DebitMyData, or its status_url while the payment confirms. Sending the same
payment again returns the same donation.

Input parameters:

- `details` (object, required): Product-specific fields. For did_registration: display_name, participant_type, controller_public_key and/or controller_wallet_address (with optional controller_network), and optionally metadata. For…
- `idempotency_key`: did_registration only: optional random key (16-128 characters) for safe retries
- `preferred_payment_option` (string, required): Payment option ID
- `product_id` (string, required): Product ID from debitmydata_catalog
- `x402_payment`: Donations only: your signed PaymentPayload (x402 version 2) answering the payment requirements this tool returned. It may also be sent in the request's _meta['x402/payment'].

### `debitmydata_complete_purchase` (~95 tokens)

Complete a purchase

Once the add-on's payment is settled: the receipt signed by DebitMyData, and the
add-on's entitlement on your DID-LLM until covers_until. Safe to call again: a completed
purchase is returned as it is. Before settlement it fails with next_action.

Input parameters:

- `purchase_id` (string, required): purchase_id from debitmydata_purchase (an add-on such as a BottyBotty tier)

### `debitmydata_whoami` (~182 tokens)

Who am I (signed in)

The DID-LLM this request is signed in as: its full DID (did, what Copy ID
copies) and short ID (did_llm_id, the DID's suffix), name, participant type, status,
entitlements, owner wallet (null: not linked), registration date and environment;
the current session apart (session: status, access, end with timezone); internal
IDs, keys and links in advanced. Sign in first. An agent: get an access token from
DebitMyData's authorization server (OAuth client credentials, with a JWT signed by
your DID-LLM's key, see llms.txt) and send it as "Authorization: Bearer <token>". An
app such as ChatGPT or Claude: its person signs in with their DID-LLM in the browser
(OAuth authorization code).

### `debitmydata_marketplace_provider_requirements` (~27 tokens)

Marketplace provider requirements

What an agent needs in order to sell through DebitMyData.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-debitmydata-agenticsuperhighway/agenticsuperhighway#diagnostics

## Score history

- 2026-11-21: 64
- 2026-11-20: 64
- 2026-11-19: 64
- 2026-11-18: 64
- 2026-11-17: 64
- 2026-11-16: 64
- 2026-11-15: 70
- 2026-11-14: 69
- 2026-11-13: 69

## Common questions

### What is the DebitMyData Agentic Superhighway MCP server?

DebitMyData Agentic Superhighway is an MCP server listed in the public MCP registry as io.debitmydata/agenticsuperhighway. Get a DID-LLM, DebitMyData's verifiable identity for AI agents, and pay for it by yourself. This page covers its hosted endpoint (https://api.debitmydata.io/agenticsuperhighway).

### Is the DebitMyData Agentic Superhighway MCP server safe to use?

DebitMyData Agentic Superhighway scores 64 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 DebitMyData Agentic Superhighway MCP server expose?

DebitMyData Agentic Superhighway exposes 21 tools: debitmydata_discover, debitmydata_get_did_registration_offer, debitmydata_open_checkout, debitmydata_list_supported_payment_options, debitmydata_create_did_payment_quote, and 16 more. Their descriptions and schemas cost roughly 2,984 tokens of context every time the server is loaded.

### Does the DebitMyData Agentic Superhighway MCP server require authentication?

No. We connected to DebitMyData Agentic Superhighway without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the DebitMyData Agentic Superhighway MCP server still maintained?

DebitMyData Agentic Superhighway 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 DebitMyData Agentic Superhighway MCP server?

VerifyMCP ran 13 checks on DebitMyData Agentic Superhighway, 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.

## Links

- Remote endpoint: https://api.debitmydata.io/agenticsuperhighway
- Repository: https://github.com/DebitMyData-PoW/agent-gateway
- Website: https://id.debitmydata.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-debitmydata-agenticsuperhighway/agenticsuperhighway.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-debitmydata-agenticsuperhighway/agenticsuperhighway/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-debitmydata-agenticsuperhighway/agenticsuperhighway.json
- HTML version of this page: https://verifymcp.io/servers/io-debitmydata-agenticsuperhighway/agenticsuperhighway
