Machine-payable API infrastructure for autonomous agents. Per-call x402 settlement in USDC.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Audits a domain's agent readiness against the aptu-readiness-1 rubric (origin headers, robots.txt, llms.txt, sitemap, agents.txt, skill.md, JSON-LD, mcp.json, A2A card, x402 manifest), weighted 0-100; rubric: https://aptu.dev/agent-readiness-checks
Domain to audit, e.g. example.com
x402 payment signature once settled
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http aptu-dev https://aptu.dev/mcp
Audits a domain's agent readiness against the aptu-readiness-1 rubric (origin headers, robots.txt, llms.txt, sitemap, agents.txt, skill.md, JSON-LD, mcp.json, A2A card, x402 manifest), weighted 0-100; rubric: https://aptu.dev/agent-readiness-checks
| Argument | Type | Description |
|---|---|---|
| domain* | string | Domain to audit, e.g. example.com |
| payment_signature | string | x402 payment signature once settled |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"domain"
],
"properties": {
"domain": {
"type": "string",
"description": "Domain to audit, e.g. example.com"
},
"payment_signature": {
"type": "string",
"description": "x402 payment signature once settled"
}
}
}BTC spot regime check against a 7-day moving average gate (bull/bear, MA7, deviation pct, favor-entry/block-entry action).
| Argument | Type | Description |
|---|---|---|
| spot* | number | BTC spot price in USD |
| closes | string | CSV of exactly 7 daily closes, oldest first |
| payment_signature | string | x402 payment signature once settled |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"spot"
],
"properties": {
"spot": {
"type": "number",
"description": "BTC spot price in USD"
},
"closes": {
"type": "string",
"description": "CSV of exactly 7 daily closes, oldest first"
},
"payment_signature": {
"type": "string",
"description": "x402 payment signature once settled"
}
}
}Echoes a JSON {message} back; the simplest paid call for verifying your x402 payment flow.
| Argument | Type | Description |
|---|---|---|
| message* | string | Message to echo back |
| payment_signature | string | x402 payment signature once settled |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"message"
],
"properties": {
"message": {
"type": "string",
"maxLength": 10000,
"description": "Message to echo back"
},
"payment_signature": {
"type": "string",
"description": "x402 payment signature once settled"
}
}
}Scores a resume 0-4 against an ATS rubric (impact, parseability, executive framing, contact).
| Argument | Type | Description |
|---|---|---|
| format* | string | Output format |
| resume_text* | string | Full resume text |
| job_description | string | Target job description |
| payment_signature | string | x402 payment signature once settled |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"resume_text",
"format"
],
"properties": {
"format": {
"enum": [
"markdown",
"typst",
"json"
],
"type": "string",
"description": "Output format"
},
"resume_text": {
"type": "string",
"description": "Full resume text"
},
"job_description": {
"type": "string",
"description": "Target job description"
},
"payment_signature": {
"type": "string",
"description": "x402 payment signature once settled"
}
}
}Seller-side x402 protocol conformance pre-flight check for a deployed resource URL (schema validation, mechanism reachability, facilitator cross-check, advisory scar-tissue findings) with a graded 0-100 report and per-failure remedies.
| Argument | Type | Description |
|---|---|---|
| url* | string | Absolute https URL of the deployed resource to probe |
| payment_signature | string | x402 payment signature once settled |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"maxLength": 2048,
"description": "Absolute https URL of the deployed resource to probe"
},
"payment_signature": {
"type": "string",
"description": "x402 payment signature once settled"
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 7, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.