Skip to main content
Glama
Sign In
1cent

1cent

by maxzoa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to 1cent

  • JMT x402 MCP Server

    jmthomasofficial
    A
    license
    B
    quality
    D
    maintenance
    Exposes 25 paid API endpoints as MCP tools for AI agents, with payments in USDC on Base mainnet via the x402 protocol, enabling tasks like web search, company intelligence, and crypto research.
    25
    111 npm
    MIT

Related Servers

  • machina-mcp

    NyTerry
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables MCP-compatible AI hosts to access URL extraction, Python security scanning, email validation, domain intelligence, and PDF inspection/extraction tools, with automatic per-call USDC payments on Base.
    MIT

  • AgentReader

    grokbot1233
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to pay per request in USDC on Base over HTTP and MCP to read web pages, extract links, check domains, research companies and UK companies, convert documents, and create webhook-based change monitors.
    MIT

  • agentreader-mcp

    ajanani1
    A
    license
    Not graded
    quality
    D
    maintenance
    MCP server providing 11 pay-per-call web intelligence tools (page reading, PDF extraction, RSS parsing, screenshots, summarization, structured data extraction) for AI agents, paid automatically in USDC via the x402 protocol on Base mainnet with no API keys required.
    36 npm
    MIT

  • Sitesy Website Intelligence

    asheeran
    A
    license
    A
    quality
    C
    maintenance
    Gives AI agents ten website and domain research tools, including full domain reports, readable page extraction, DNS lookups, feed and sitemap parsing, link and metadata extraction, site checks, and redirect tracing. Calls are paid per use in USDC on Base via x402 from a configured wallet, so no account, API key, or subscription is required.
    10
    578 npm
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.3/5.0

Scored across 35 tools

Disambiguation4/5

Each tool targets a very specific aspect of URL analysis with clear descriptions, making them mostly distinguishable. However, the high granularity (e.g., url_headers vs url_security_headers) may cause minor confusion for an agent without deep familiarity.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with prefixes (url_, site_, demo_, catalog_) and use snake_case throughout. No mixing of conventions, making it predictable.

Tool Count3/5

35 tools is high for a single domain like URL analysis. While each serves a specific need, the granularity is extreme and could be simplified by combining some functions into parameters. Still, the count is not egregious given the breadth of coverage.

Completeness5/5

The tool set covers virtually every aspect of public URL inspection: availability, content, metadata, security, robots, sitemaps, feeds, OpenAPI, TLS, etc. No obvious gaps exist for the stated purpose.

Maintenance

ActivityStale
ResponsivenessLimited data

Resources