conway

Conway MCP Server

APIMesh brings paid website diagnostics and developer utilities into MCP-compatible AI assistants. It serves agents and developers checking performance, SEO, security, domains, and API behavior, with wallet spending controls and several payment options.

Server facts

conway MCP Server

Project

Author
mbeato
License
MIT

Tech

Runtime / language
node
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
6
Last commit
Data as of

Tags

  • Crypto
  • Seo
  • base
  • micropayments
  • security
  • usdc
  • web analysis
  • x402

Overview

APIMesh organizes website investigation around checks for performance, search visibility, security, and infrastructure. An assistant can inspect Lighthouse results, trace redirects, examine crawl restrictions, review page metadata, and identify technologies from headers and HTML. Domain workflows include email authentication checks, brand availability searches, and asset extraction. Security tools cover certificates, HTTP headers, cookies, subdomain exposure, and configuration issues, while DNS and IP utilities examine propagation and infrastructure details. Developers can also validate YAML, create test JWTs, generate OpenAPI fragments, compare API schemas, and test regular expressions.

The MCP integration uses stdio and supports clients including Claude, Cursor, Windsurf, and Cline. Most APIs provide limited free previews before paid use. Payment routes include x402 with USDC on Base, Stripe MPP, and API keys backed by purchased credits. Wallet tools report spending and remaining budgets, and let callers configure daily or monthly caps that block further paid requests when reached. Beyond its callable tools, the project describes an automated loop for identifying demand, generating API code, testing it, auditing it, and deploying new services.

conway setup notes

  • conway records stdio only; confirm a network transport upstream before planning remote access.

Related MCP servers