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.
ENDPOINT 1
https://api.micropay.website/mcp
MCP server metadata
- Name
- Micropay
- Version
- 1.0.0
Known tools 3
compile_puya_tsCompile an Algorand TypeScript project with Puya and return diagnostics and TEAL.
Inferred read-onlyCONNECT 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.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.