Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

DebitMyData Agentic Superhighway

REMOTE · API.DEBITMYDATA.IO

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

−5 this week 64 Trust /100

Last scanned (19 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Recent critical change

Authorization (16 Nov 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: schema churn in the 8 days we've observed: 16 tool removals, 0 breaking changes, 0 auth/transport breaks, 21 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (90% 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
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 22 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
What we tested

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 →

Changelog

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 0
    • Server version: 0.55.17 → 0.55.22 functional
  • 19 Nov 26 0
    • Tool “debitmydata_whoami” rewrote its description, which is the text the model reads security
    • Server version: 0.55.14 → 0.55.17 functional
  • 18 Nov 26 0
    • Server version: 0.55.12 → 0.55.14 functional
  • 17 Nov 26 0
    • Server version: 0.55.10 → 0.55.12 functional
  • 16 Nov 26 −6
    • Authorization: partial → fail ▼ critical
    • Stability: 0.07 → fail ▼ security
    • Tool “dmd_catalog” was removed ▼ security
    • Tool “dmd_complete_purchase” was removed ▼ security
    • Tool “dmd_create_did_payment_quote” was removed ▼ security
    • Tool “dmd_discover” was removed ▼ security
    • Tool “dmd_get_did_registration_offer” was removed ▼ security
    • Tool “dmd_get_payment_status” was removed ▼ security
    • Tool “dmd_get_purchase_quote” was removed ▼ security
    • Tool “dmd_get_registration_status” was removed ▼ security
    • Tool “dmd_list_in_directory” was removed ▼ security
    • Tool “dmd_list_supported_payment_options” was removed ▼ security
    • Tool “dmd_marketplace_provider_requirements” was removed ▼ security
    • Tool “dmd_open_checkout” was removed ▼ security
    • Tool “dmd_prove_wallet_control” was removed ▼ security
    • Tool “dmd_purchase” was removed ▼ security
    • Tool “dmd_register_did” was removed ▼ security
    • Tool “dmd_search_directory” was removed ▼ security
    • Tool “dmd_submit_payment_reference” was removed ▼ security
    • Tool “dmd_verify_agent” was removed ▼ security
    • Tool “dmd_whoami” was removed ▼ security
    • 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 security
    • Schema quality: 3217 → 3799 ▼ functional
    • 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” functional
  • 15 Nov 26 +1
    • 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 security
    • 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” functional
  • 14 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 0.36.0 → 0.37.2 functional
  • 13 Nov 26 69

    First indexed and scored.

Diagnostics

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://api.debitmydata.io/agenticsuperhighway

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=debitmydata.io CN=WE1,O=Google Trust Services,C=US 17 Oct 2026 15 Jan 2027 ECDSA 256 ECDSA-SHA256 3331717e166b2a911363ea80e83cf7a5
SANs: debitmydata.io, *.debitmydata.io
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 api.debitmydata.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
debitmydata.io. 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
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://api.debitmydata.io/agenticsuperhighway Verified 200
http (plaintext) http://api.debitmydata.io/agenticsuperhighway HTTPS enforced 301 https://api.debitmydata.io/agenticsuperhighway
MCP tools · 21 exposed · ~2,984 tokens

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 →

Tool Tokens
debitmydata_catalog ~50

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.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

debitmydata_change_owner ~297

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.

NameTypeReqDescription
challenge_id––The message you signed (from `messages`)
change_id––Leave empty to start a change; then the change_id it returned
didstringyesThe 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

Structured output declared, but exposes no named fields.

No examples provided.

debitmydata_complete_purchase ~95

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.

NameTypeReqDescription
purchase_idstringyespurchase_id from debitmydata_purchase (an add-on such as a BottyBotty tier)

Structured output declared, but exposes no named fields.

No examples provided.

debitmydata_create_did_payment_quote ~279

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.

NameTypeReqDescription
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_namestringyesPublic 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–yesWhat kind of participant
preferred_payment_optionstringyesPayment option ID from the offer, e.g. dmd_pow_native

Structured output declared, but exposes no named fields.

No examples provided.

debitmydata_discover ~85

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.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

debitmydata_get_did_registration_offer ~51

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

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

debitmydata_get_payment_status ~61

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

NameTypeReqDescription
payment_intent_idstringyespayment_intent_id from the quote (dmd_payment_intent_...)

Structured output declared, but exposes no named fields.

No examples provided.

debitmydata_get_purchase_quote ~61

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.

NameTypeReqDescription
product_idstringyesProduct ID from debitmydata_catalog

Structured output declared, but exposes no named fields.

No examples provided.

debitmydata_get_registration_status ~57

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

NameTypeReqDescription
registration_intent_idstringyesregistration_intent_id from the quote (dmd_did_intent_...)

Structured output declared, but exposes no named fields.

No examples provided.

debitmydata_list_in_directory ~251

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.

NameTypeReqDescription
challenge_id––Leave empty to get the message to sign
controller_type––Who signs: ed25519 (the key, by default) or eip155 (the wallet)
didstringyesThe DID-LLM (did:web:...:agents:...) or its identity ID (dmd_identity_...)
listedboolean–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

Structured output declared, but exposes no named fields.

No examples provided.

debitmydata_list_supported_payment_options ~49

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

NameTypeReqDescription
servicestring–Service ID, e.g. did_registration

Structured output declared, but exposes no named fields.

No examples provided.

debitmydata_marketplace_provider_requirements ~27

What an agent needs in order to sell through DebitMyData.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

debitmydata_open_checkout ~98

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.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

debitmydata_prove_wallet_control ~196

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).

NameTypeReqDescription
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_idstringyesregistration_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

Structured output declared, but exposes no named fields.

No examples provided.

debitmydata_purchase ~387

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.

NameTypeReqDescription
detailsobjectyesProduct-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_optionstringyesPayment option ID
product_idstringyesProduct 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'].

No output schema declared.

No examples provided.

debitmydata_register_did ~199

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.

NameTypeReqDescription
registration_intent_idstringyesregistration_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'].

No output schema declared.

No examples provided.

debitmydata_revoke_did ~210

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).

NameTypeReqDescription
challenge_id––Leave empty to get the message to sign
controller_type––Who signs: ed25519 (the key, by default) or eip155 (the wallet)
didstringyesThe 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

Structured output declared, but exposes no named fields.

No examples provided.

debitmydata_search_directory ~88

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.

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

Structured output declared, but exposes no named fields.

No examples provided.

debitmydata_submit_payment_reference ~80

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

NameTypeReqDescription
payment_intent_idstringyespayment_intent_id from the quote (dmd_payment_intent_...)
transaction_referencestringyesTransaction ID / hash of the payment you broadcast

Structured output declared, but exposes no named fields.

No examples provided.

debitmydata_verify_agent ~181

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).

NameTypeReqDescription
audience––Who verifies (your name or site), written in the challenge
didstringyesThe 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)

Structured output declared, but exposes no named fields.

No examples provided.

debitmydata_whoami ~182

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).

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

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.

remote · api.debitmydata.io

# add to Claude Code
claude mcp add --transport http io-debitmydata-agenticsuperhighway 'https://api.debitmydata.io/agenticsuperhighway'
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.