# aptu.dev (remote · aptu.dev)

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

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

## Components

- remote · `aptu.dev`: 72/100 (this document), [markdown](https://verifymcp.io/servers/aptu-dev-aptu-dev/aptu.md), [page](https://verifymcp.io/servers/aptu-dev-aptu-dev/aptu)

## Channel facts

- Endpoint: `https://aptu.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1034 tokens (~79/item across 13 items; 13 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 13 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 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.

### Claude

```bash
claude mcp add --transport http aptu-dev-aptu-dev 'https://aptu.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "aptu-dev-aptu-dev": {
      "url": "https://aptu.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "aptu-dev-aptu-dev": {
      "type": "http",
      "url": "https://aptu.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.aptu-dev-aptu-dev]
url = "https://aptu.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "aptu-dev-aptu-dev": {
      "type": "remote",
      "url": "https://aptu.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add aptu-dev-aptu-dev --url 'https://aptu.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  aptu-dev-aptu-dev:
    url: "https://aptu.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "aptu-dev-aptu-dev": {
      "Transport": "http",
      "Url": "https://aptu.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add aptu-dev-aptu-dev -t streamable-http -u 'https://aptu.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "aptu-dev-aptu-dev": {
      "type": "http",
      "url": "https://aptu.dev/mcp"
    }
  }
}
```

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 72, +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.

### 2026-11-18 (score 71, +1)

- [security] 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
- [functional regression] Schema quality: 893 → 1034
- [functional] New tool “judge_dry_run”
- [functional] New tool “verify_receipt”

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

- [functional regression] Schema quality: 770 → 893
- [functional] New tool “judge”

### 2026-11-15 (score 69, +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.

### 2026-11-13 (score 68, +2)

- [security improvement] DNSSEC: fail → pass

### 2026-11-12 (score 66, 0)

- [security] 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
- [functional improvement] Schema quality: 86 → 77
- [functional] New tool “rbq_resolve”
- [functional] New tool “regime_verdict”
- [functional] New tool “req_resolve”
- [functional] New tool “sol_regime”

### 2026-11-10 (score 66, +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.

### 2026-11-08 (score 65, −1)

- [security regression] DNSSEC: pass → fail
- [functional regression] Schema quality: 408 → 516
- [functional improvement] Stability: unverified → 0.03
- [functional] New tool “readiness_fix”

## MCP tools (13)

### `echo_probe` (~54 tokens)

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

Input parameters:

- `message` (string, required): Message to echo back
- `payment_signature` (string): x402 payment signature once settled

### `resume_eval` (~75 tokens)

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

Input parameters:

- `format` (string, required): Output format
- `job_description` (string): Target job description
- `payment_signature` (string): x402 payment signature once settled
- `resume_text` (string, required): Full resume text

### `agent_readiness` (~77 tokens)

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

Input parameters:

- `domain` (string, required): Domain to audit, e.g. example.com
- `payment_signature` (string): x402 payment signature once settled

### `btc_regime` (~81 tokens)

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

Input parameters:

- `closes` (string): CSV of exactly 7 daily closes, oldest first
- `payment_signature` (string): x402 payment signature once settled
- `spot` (number, required): BTC spot price in USD

### `sol_regime` (~81 tokens)

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

Input parameters:

- `closes` (string): CSV of exactly 7 daily closes, oldest first
- `payment_signature` (string): x402 payment signature once settled
- `spot` (number, required): SOL spot price in USD

### `req_resolve` (~98 tokens)

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.

Input parameters:

- `limit` (integer): Maximum matches to return (default 10, max 25)
- `payment_signature` (string): x402 payment signature once settled
- `q` (string, required): NEQ (10 digits) or enterprise name to resolve

### `rbq_resolve` (~89 tokens)

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.

Input parameters:

- `payment_signature` (string): x402 payment signature once settled
- `q` (string, required): RBQ licence number (10 digits), NEQ, or holder name prefix

### `regime_verdict` (~54 tokens)

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

Input parameters:

- `payment_signature` (string): x402 payment signature once settled

### `x402_preflight` (~80 tokens)

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

Input parameters:

- `payment_signature` (string): x402 payment signature once settled
- `url` (string, required): Absolute https URL of the deployed resource to probe

### `readiness_fix` (~72 tokens)

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

Input parameters:

- `domain` (string, required): Domain to generate fixes for, e.g. example.com
- `payment_signature` (string): x402 payment signature once settled

### `judge` (~135 tokens)

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

Input parameters:

- `payment_signature` (string): x402 payment signature once settled
- `questions` (object, required): Map of name to question spec: {type: noul|choice|score, instructions, criteria?}. 1-25 questions.
- `state` (required): Application state the questions judge.
- `timeout_ms` (integer): Optional per-request timeout cap in ms (max 60000).

### `judge_dry_run` (~70 tokens)

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

Input parameters:

- `questions` (object, required): Map of name to question spec: {type: noul|choice|score, instructions, criteria?}.
- `state` (required): Application state the questions judge.

### `verify_receipt` (~68 tokens)

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

Input parameters:

- `attestation` (object, required): The attestation object from a settled judge response.
- `jwks` (object): Optional inline JWKS; fetched from the published endpoint when omitted.

## Diagnostics

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

## Score history

- 2026-11-21: 72
- 2026-11-20: 71
- 2026-11-19: 71
- 2026-11-18: 71
- 2026-11-17: 70
- 2026-11-16: 69
- 2026-11-15: 69
- 2026-11-14: 68
- 2026-11-13: 68
- 2026-11-12: 66
- 2026-11-11: 66
- 2026-11-10: 66
- 2026-11-09: 65
- 2026-11-08: 65
- 2026-11-07: 66

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

## Links

- Remote endpoint: https://aptu.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/aptu-dev-aptu-dev/aptu.xml
- Changelog JSON feed: https://verifymcp.io/servers/aptu-dev-aptu-dev/aptu/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/aptu-dev-aptu-dev/aptu.json
- HTML version of this page: https://verifymcp.io/servers/aptu-dev-aptu-dev/aptu
