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.

aptu.dev

REMOTE · APTU.DEV

Machine-payable API infrastructure for autonomous agents. Per-call x402 settlement in USDC.

Available components

+4 this week 72 Trust /100

Last scanned (14 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

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 Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation not fully verified: no authorisation is required to call this server, and 13 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1034 tokens (~79/item across 13 items; 13 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "resume_eval" implies "eval" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 13 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 (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 13 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

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 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1
    • Tool “judge” rewrote its description, which is the text the model reads security
    • Tool “req_resolve” rewrote its description, which is the text the model reads security
    • Schema quality: 893 → 1034 ▼ functional
    • New tool “judge_dry_run” functional
    • New tool “verify_receipt” functional
  • 17 Nov 26 +1
    • Schema quality: 770 → 893 ▼ functional
    • New tool “judge” functional
  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +2
    • DNSSEC: fail → pass ▲ security
  • 12 Nov 26 0
    • Tool “agent_readiness” rewrote its description, which is the text the model reads security
    • Tool “readiness_fix” rewrote its description, which is the text the model reads security
    • Tool “x402_preflight” rewrote its description, which is the text the model reads security
    • Schema quality: 86 → 77 ▲ functional
    • New tool “rbq_resolve” functional
    • New tool “regime_verdict” functional
    • New tool “req_resolve” functional
    • New tool “sol_regime” functional
  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Nov 26 −1
    • DNSSEC: pass → fail ▼ security
    • Schema quality: 408 → 516 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • New tool “readiness_fix” functional
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://aptu.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=aptu.dev CN=WE1,O=Google Trust Services,C=US 15 Nov 2026 13 Feb 2027 ECDSA 256 ECDSA-SHA256 ba84d44e83a1568613121d582d1d68f1
SANs: aptu.dev, badge-backend.aptu.dev, *.badge-backend.aptu.dev
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 secure

Validation of aptu.dev. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
aptu.dev. DS published 2371 13 Verified
aptu.dev. Verified address RRset verified with the apex keys
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=15552000
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://aptu.dev/mcp Verified 200
http (plaintext) http://aptu.dev/mcp HTTPS enforced 301 https://aptu.dev/mcp
MCP tools · 13 exposed · ~1,034 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
agent_readiness ~77

Audits a domain's agent readiness against the aptu-readiness-1 rubric, weighted 0-100; full rubric: https://aptu.dev/agent-readiness-checks

NameTypeReqDescription
domainstringyesDomain to audit, e.g. example.com
payment_signaturestring–x402 payment signature once settled

No output schema declared.

No examples provided.

btc_regime ~81

BTC spot regime check against a 7-day moving average gate (bull/bear, MA7, deviation pct, favor-entry/block-entry action).

NameTypeReqDescription
closesstring–CSV of exactly 7 daily closes, oldest first
payment_signaturestring–x402 payment signature once settled
spotnumberyesBTC spot price in USD

No output schema declared.

No examples provided.

echo_probe ~54

Echoes a JSON {message} back; the simplest paid call for verifying your x402 payment flow.

NameTypeReqDescription
messagestringyesMessage to echo back
payment_signaturestring–x402 payment signature once settled

No output schema declared.

No examples provided.

judge ~135

Typed judging: the Clef model answers your noul, choice, or score questions about JSON state; returns calibrated answers, a settlement receipt, and an Ed25519-signed attestation (JWKS: /.well-known/jwks.json).

NameTypeReqDescription
payment_signaturestring–x402 payment signature once settled
questionsobjectyesMap of name to question spec: {type: noul|choice|score, instructions, criteria?}. 1-25 questions.
state–yesApplication state the questions judge.
timeout_msinteger–Optional per-request timeout cap in ms (max 60000).

No output schema declared.

No examples provided.

judge_dry_run ~70

Validate a judge request spec for free: reports validity, question count, and the price of a paid run.

NameTypeReqDescription
questionsobjectyesMap of name to question spec: {type: noul|choice|score, instructions, criteria?}.
state–yesApplication state the questions judge.

No output schema declared.

No examples provided.

rbq_resolve ~89

Resolves a Quebec construction licence by 10-digit RBQ licence number, NEQ, or holder name prefix against the official RBQ licencesactives open-data index; returns the licence record with data-date provenance.

NameTypeReqDescription
payment_signaturestring–x402 payment signature once settled
qstringyesRBQ licence number (10 digits), NEQ, or holder name prefix

No output schema declared.

No examples provided.

readiness_fix ~72

Re-probes a domain and returns ready-to-host machine-surface artifacts from probe facts; contract: https://aptu.dev/readiness-fix-checks

NameTypeReqDescription
domainstringyesDomain to generate fixes for, e.g. example.com
payment_signaturestring–x402 payment signature once settled

No output schema declared.

No examples provided.

regime_verdict ~54

Combined BTC and SOL regime verdict: both spot-vs-MA7 gates plus a crossRail alignment field (aligned when both actions match, divergent otherwise).

NameTypeReqDescription
payment_signaturestring–x402 payment signature once settled

No output schema declared.

No examples provided.

req_resolve ~98

Resolves a Quebec enterprise by 10-digit NEQ or name against the official Registraire des entreprises open-data index (bimonthly refresh); returns the record with source attribution.

NameTypeReqDescription
limitinteger–Maximum matches to return (default 10, max 25)
payment_signaturestring–x402 payment signature once settled
qstringyesNEQ (10 digits) or enterprise name to resolve

No output schema declared.

No examples provided.

resume_eval ~75

Scores a resume 0-4 against an ATS rubric (impact, parseability, executive framing, contact).

NameTypeReqDescription
formatstringyesOutput format
job_descriptionstring–Target job description
payment_signaturestring–x402 payment signature once settled
resume_textstringyesFull resume text

No output schema declared.

No examples provided.

sol_regime ~81

SOL spot regime check against a 7-day moving average gate (bull/bear, MA7, deviation pct, favor-entry/block-entry action).

NameTypeReqDescription
closesstring–CSV of exactly 7 daily closes, oldest first
payment_signaturestring–x402 payment signature once settled
spotnumberyesSOL spot price in USD

No output schema declared.

No examples provided.

verify_receipt ~68

Verify an Ed25519 judge receipt attestation offline against the published JWKS; no payment or upstream call.

NameTypeReqDescription
attestationobjectyesThe attestation object from a settled judge response.
jwksobject–Optional inline JWKS; fetched from the published endpoint when omitted.

No output schema declared.

No examples provided.

x402_preflight ~80

Graded 0-100 x402 protocol conformance pre-flight check for a deployed resource URL, with per-failure remedies; rubric: https://aptu.dev/x402-preflight-checks

NameTypeReqDescription
payment_signaturestring–x402 payment signature once settled
urlstringyesAbsolute https URL of the deployed resource to probe

No output schema declared.

No examples provided.

Install

How do I install the aptu.dev MCP server?

aptu.dev is a hosted endpoint at https://aptu.dev/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 · aptu.dev

# add to Claude Code
claude mcp add --transport http aptu-dev-aptu-dev 'https://aptu.dev/mcp'
Common questions

What is the aptu.dev MCP server?

aptu.dev is an MCP server listed in the public MCP registry as io.github.aptu-dev/aptu-dev. Machine-payable API infrastructure for autonomous agents. Per-call x402 settlement in USDC. This page covers its hosted endpoint (https://aptu.dev/mcp).

Is the aptu.dev MCP server safe to use?

aptu.dev scores 72 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 aptu.dev MCP server expose?

aptu.dev exposes 13 tools: echo_probe, resume_eval, agent_readiness, btc_regime, sol_regime, and 8 more. Their descriptions and schemas cost roughly 1,034 tokens of context every time the server is loaded.

Does the aptu.dev MCP server require authentication?

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

Is the aptu.dev MCP server still maintained?

aptu.dev 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 aptu.dev MCP server?

VerifyMCP ran 12 checks on aptu.dev, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about aptu.dev: Authorization. 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.