AIPP Monetize
REMOTE · AIPP.DEV · SCANNED OCT 3
Pay-per-action access to APIs and MCP tools over Lightning L402 and Base USDC x402.
Available components
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 Security57
- 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 3 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 148 tokens (~49/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the AIPP Monetize MCP server?
AIPP Monetize is a hosted endpoint at https://aipp.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 · aipp.dev
claude mcp add --transport http dev-aipp-monetize 'https://aipp.dev/mcp'
{
"mcpServers": {
"dev-aipp-monetize": {
"url": "https://aipp.dev/mcp"
}
}
} {
"servers": {
"dev-aipp-monetize": {
"type": "http",
"url": "https://aipp.dev/mcp"
}
}
} [mcp_servers.dev-aipp-monetize] url = "https://aipp.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-aipp-monetize": {
"type": "remote",
"url": "https://aipp.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-aipp-monetize --url 'https://aipp.dev/mcp' --transport streamable-http
mcp_servers:
dev-aipp-monetize:
url: "https://aipp.dev/mcp" {
"McpServers": {
"dev-aipp-monetize": {
"Transport": "http",
"Url": "https://aipp.dev/mcp"
}
}
} assistant mcp add dev-aipp-monetize -t streamable-http -u 'https://aipp.dev/mcp'
{
"mcpServers": {
"dev-aipp-monetize": {
"type": "http",
"url": "https://aipp.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 29 Sept 26 +1
- Stability: 0.97 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
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 3 Oct 2026 · Probed https://aipp.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.aipp.dev | CN=YR1,O=Let's Encrypt,C=US | 30 Sept 2026 | 29 Dec 2026 | RSA 4096 | SHA256-RSA | 6f6663a8d4f90efa72e7c44189ab315574d |
| SANs: aipp.dev, www.aipp.dev | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of aipp.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| aipp.dev. | absent | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://aipp.dev/mcp | Verified | 200 | |
| http (plaintext) | http://aipp.dev/mcp | HTTPS enforced | 301 | https://aipp.dev/mcp |
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 →
get_aipp_capabilities ~47
Explains AIPP pay-per-action monetization capabilities for APIs, MCP tools, automations, and digital resources over Lightning (L402) and Base USDC (x402).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_integration_guide ~37
Returns integration instructions, flow steps, and official documentation links for a target type.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Integration target type |
No output schema declared.
No examples provided.
inspect_smart_tag ~64
Inspects a public AIPP Smart Tag by ID or URL and returns its public manifest, pricing, and accepted payment rails.
| Name | Type | Req | Description |
|---|---|---|---|
| tag_id_or_url | string | yes | AIPP Smart Tag ID (e.g. demo) or full aipp.dev Smart Tag URL |
No output schema declared.
No examples provided.
What is the AIPP Monetize MCP server?
AIPP Monetize is an MCP server listed in the public MCP registry as dev.aipp/monetize. Pay-per-action access to APIs and MCP tools over Lightning L402 and Base USDC x402. This page covers its hosted endpoint (https://aipp.dev/mcp).
Is the AIPP Monetize MCP server safe to use?
AIPP Monetize scores 79 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 AIPP Monetize MCP server expose?
AIPP Monetize exposes 3 tools: get_aipp_capabilities, get_integration_guide, inspect_smart_tag. Their descriptions and schemas cost roughly 148 tokens of context every time the server is loaded.
Does the AIPP Monetize MCP server require authentication?
No. We connected to AIPP Monetize without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AIPP Monetize MCP server still maintained?
AIPP Monetize is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.