A
licenseNot graded
qualityC
maintenanceEnables AI agents to make pay-per-call USDC payments on Base via x402 for headless page rendering, temporary file hosting, scheduled callbacks, and pump.fun launch and trend feeds.
MIT
baconservices-mcp
by afmontoya
Related Servers
Alternatives to baconservices-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to securely access x402-protected APIs on Base L2 with automatic USDC payments under deterministic spending limits, domain and contract allowlists, transaction simulation, and audit logging.4764 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to discover, pay for, and invoke x402-priced services such as document OCR, document analysis, media transcription, remote browser sessions, and receive-only email inboxes using USDC on Base, with no API keys and receipt-backed results.38MIT
@bridgenode/mcpofficial
AlicenseAqualityCmaintenanceEnables AI agents to make pay-as-you-go AI inference requests through x402 with automatic Solana USDC payments, no API keys or registration, while enforcing configurable spending limits.3196 npm1MIT No Attribution- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access 21 mazzagrp.com AI endpoints with x402 USDC micropayments on Base, paying per call without API keys.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to discover and invoke x402-monetized computational engines for media geometry, measurements, JSON hygiene, and ComfyUI preflight audits, with USDC settlement on Base Mainnet.-
TDQS
A4.1/5.0
Scored across 10 tools
Disambiguation4/5
Each tool maps to a distinct operation: four clearly separate image transforms (palette extraction, optimization, background removal, vectorization) and three distinct page analyses (brand data, SEO metadata, WCAG checks). The one soft overlap is brand_from_url vs page_metadata, since both fetch the same page and return overlapping metadata, but their stated outputs (brand assets vs SEO/preview signals) are different enough for correct selection.
Naming Consistency3/5
All names use consistent snake_case, but the conventions are mixed: about half are verb_noun (list_services, optimize_image, remove_background, vectorize_image) and half are noun_phrases (image_palette, page_metadata, wallet_status, accessibility_check). Names remain readable and largely self-explanatory, but an agent cannot infer the pattern from one name to another.
Tool Count5/5
Ten tools is well within the ideal range and each one earns its place: four image services, three page-analysis services, plus catalog/quote/wallet tooling. No tool looks like filler or a near-duplicate.
Completeness4/5
The payment lifecycle is well covered (list_services, quote, wallet_status plus per-call pricing) and the service surface is coherent for an image/web analysis catalog. Minor gaps: no way to set or adjust spending limits, no transaction history/receipts, and result retrieval depends on save_to rather than a job-status tool, but these are workable.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues