← Registry

Developer Tools

micropay.website

An MCP server that exposes Micropay AI model pricing and paid x402 HTTP resources while also compiling Algorand TypeScript projects with Puya.

x402 supported1 endpoint3 known toolsFirst detected October 19, 2026Last detected October 19, 2026

ENDPOINT 1

https://api.micropay.website/mcp

No auth detected

MCP server metadata

Name
Micropay
Version
1.0.0
Capabilities
tools.listChanged

Known tools 3

list_models

List Micropay AI models with their current per-call USDC prices.

Inferred read-only
micropay_endpoints

List the paid x402 HTTP resources exposed by Micropay.

Inferred read-only
compile_puya_ts

Compile an Algorand TypeScript project with Puya and return diagnostics and TEAL.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.micropay]
url = "https://api.micropay.website/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "micropay": {
      "type": "http",
      "url": "https://api.micropay.website/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: micropay
Remote MCP URL: https://api.micropay.website/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "micropay": {
      "url": "https://api.micropay.website/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "micropay": {
      "type": "http",
      "url": "https://api.micropay.website/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "micropay",
  "transport": "streamable-http",
  "url": "https://api.micropay.website/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.