
Apimesh
io.github.mbeatoPublished by GitHub account mbeatov1.8.2Updated Oct 24, 2026
74 paid web-analysis APIs (SEO, security, TLS, DNS, email) as MCP tools. USDC via x402.
Overview
Paid web-analysis APIs (SEO, security, TLS, DNS, email, dev utilities) exposed as MCP tools, paid per call with USDC or cards.
- What you can do
- Run website audits: Core Web Vitals, security headers, SEO, indexability, redirect chains, tech stack, favicons and HTTP status
- Check domains and email: SPF/DKIM/DMARC, MX records, email verification, WHOIS/DNS/SSL intelligence, brand-name availability
- Run developer utilities: regex building, YAML validation, mock JWT generation, user-agent parsing, status-code lookup, OpenAPI docs
- Check service health and validate web resources such as robots.txt, sitemap.xml and openapi.json
- Query wallet spend summaries, transaction history and spend caps
- When to use it
- Useful when an assistant needs on-demand website audits, SEO or security-header checks, domain and email verification, or small developer utilities without signing up for separate services. Free preview endpoints let you test an API before paying.
- Requirements
- Runs locally via npx from the npm package @mbeato/apimesh-mcp-server (Node.js). Network access to the apimesh.xyz endpoints is required. Paid calls need a payment method: USDC on Base via the x402 X-PAYMENT header, Stripe card payments, or an API key with purchased credits. No environment variables are declared.
Installation
In SourceWeft
- Open Apimesh in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
APIMesh
[npm version] [npm downloads] [APIs] [MCP Tools] [License: MIT] [Payments]
Pay-per-call web analysis APIs for AI agents and developers. Security audits, performance monitoring, SEO analysis, email verification, tech stack detection, and more -- no signup required, just pay with USDC on Base and get your response.
APIMesh is a collection of 102 focused web analysis APIs, each on its own subdomain, with a 67-tool MCP server for direct use in Claude, Cursor, Windsurf, Cline, and any MCP-compatible client. Every endpoint supports three payment methods: crypto micropayments via x402, card payments via Stripe MPP, and traditional API keys via Stripe checkout.
Live Site -- Dashboard -- npm -- MCP Registry -- Smithery
Quick Start
Try free previews (no payment, no signup)
Install the MCP server
One command to add all 67 tools to your AI coding assistant:
Or add to your MCP client config (claude_desktop_config.json, .cursor/mcp.json, etc.):
Direct API usage
All APIs
Every API lives on its own subdomain: https://{api-name}.apimesh.xyz
Web Analysis APIs
Developer Utility APIs
Autonomously Built APIs
These APIs were built, tested, and deployed by APIMesh's autonomous brain loop — no human wrote the code:
New APIs are added automatically as the brain discovers demand and builds solutions. See How the Brain Works below.
Wallet & Spend Tracking (free, no auth)
Payment Methods
APIMesh supports three ways to pay:
1. x402 -- crypto micropayments (default)
No accounts. No API keys. No subscriptions. The agent handles payment autonomously.
- Protocol: x402 (open standard)
- Currency: USDC on Base (chain ID 8453)
- Facilitator: Coinbase CDP
2. MPP -- Stripe Machine Payments Protocol
Stripe MPP enables AI agents to pay with cards or stablecoins through Stripe's infrastructure.
3. API key + credits
Traditional auth for developers who prefer it. Purchase credits via Stripe checkout and include your API key in requests.
Discovery & Integration
Most APIs offer free /preview endpoints so agents can verify functionality before paying. Every API has free /health and / info endpoints.
The Autonomous Brain
APIMesh has an autonomous build loop that runs daily on the server. It discovers demand, generates APIs, tests them, and deploys to production — no human in the loop. It also maintains the awesome-mpp ecosystem directory.
Hardened against prompt injection: external signal data is sanitized, LLM prompts use system-role security rules, generated code is audited for 14+ vulnerability patterns, and the test environment is sandboxed with .env isolation.
The brain currently uses OpenAI (gpt-4.1-mini) for code generation and scores opportunities based on demand, implementation depth, and competitive differentiation.
Tech Stack
- Bun -- runtime and bundler
- Hono -- web framework
- x402 + MPP -- payment protocols
- Caddy -- reverse proxy with automatic HTTPS
- SQLite -- analytics and usage tracking
- OpenAI -- autonomous API generation
Related
- awesome-mpp -- the MPP ecosystem registry (100+ projects)
Contributing
Contributions are welcome. If you find a bug or want to suggest a new API tool, open an issue or start a discussion.
To run locally:
License
Source: README.md at commit b0d111f
Tools
0Version history
1- v1.8.2LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts