1cent
Provides a Telegram interface for administrative tasks such as managing the MCP server.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@1centsearch the catalog for AI agent tools"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
1cent Web Intelligence for AI Agents
Give AI agents safe, bounded web intelligence without subscriptions, API keys or handing a crawler unrestricted network access. Start with three free MCP tools; pay only for the URL operation used. Production uses x402 v2, Base Mainnet USDC and PayAI.
Try the real safe fetch path in one command — fixed example.com, no payment:
curl -sS https://1cent.maxzoa.ru/v1/demo/live-pulseMCP:
https://1cent.maxzoa.ru/mcpFree product demo:
https://1cent.maxzoa.ru/v1/demo/pulseFree live demo:
https://1cent.maxzoa.ru/v1/demo/live-pulseLive catalog/prices:
https://1cent.maxzoa.ru/v1/catalogPublic trust status:
https://1cent.maxzoa.ru/status.jsonBuyer guide:
https://1cent.maxzoa.ru/docs/getting-started
Production exposes 32 paid REST/MCP operations plus three free MCP tools:
catalog_search— find the correct operation and live price without a URL fetch;demo_url_pulse— inspect a fixed precomputed output sample without payment or network access.demo_live_url_pulse— run the real safe service against fixedexample.com, rate-limited.
MCP also publishes one buyer prompt (choose_url_tool) and one static buyer-guide resource
(onecent://buyer-guide). Every input field includes constraints, examples and machine-readable
descriptions so agents can choose and call tools correctly on the first attempt.
Find 1cent
Official MCP Registry:
ru.maxzoa/1cent;Glama remote connector:
https://glama.ai/mcp/connectors/ru.maxzoa/1cent;Smithery:
https://smithery.ai/servers/maxzoa27/onecent;MCP.so:
https://mcp.so/servers/1cent;LobeHub:
https://lobehub.com/mcp/maxzoa-1cent.
Glama release verification uses the repository's onecent-glama stdio entry point. It loads the
same MCP tool registry as production for schema inspection; it does not provide a payment bypass
or a second implementation of paid URL operations.
Directory status is checked with dated evidence in Marketplace quality report. A page returning HTTP 200 alone is not counted as a successful listing: it must be searchable, current and installable.
Buyer setup starts with a no-payment diagnostic:
onecent doctorFor MCP clients without native x402 signing, install the local Buyer Bridge:
pipx install "onecent[buyer] @ git+https://github.com/maxzoa/1cent.git"
onecent wallet set
onecent bridge --max-usdc-per-call 0.001 --daily-limit-usdc 0.01Manual one-call approval is the default. The OS keyring holds the buyer secret; 1cent, remote MCP and catalog services never receive it. UNKNOWN outcomes are never retried. See Buyer Bridge for Claude, Cursor, VS Code and Codex setup.
The direct CLI also refuses a paid call unless the buyer explicitly supplies a maximum amount,
confirms Base Mainnet and types the one-call confirmation. See examples/buyer-python and
examples/buyer-node.
PostgreSQL is the runtime source for tool availability and atomic Base USDC prices. Config values are clean-install fallbacks. Paid URL work begins only after successful payment checks.
Related MCP server: TensorFeed MCP Server
Safety contract
public HTTP/HTTPS only; private, loopback, link-local and rebinding destinations fail closed;
strict input schemas; unknown fields rejected;
bounded redirects, response bodies, extracted text, concurrency and queue depth;
payment identifier, request fingerprint and idempotent replay protection;
UNKNOWN settlement never retried automatically;
no seller private key, buyer key, Docker socket or JavaScript execution on the server;
Streamable HTTP host/origin protection enabled for remote MCP.
Local quality checks
python -m venv .venv
.venv/Scripts/pip install --require-hashes -r requirements-dev.lock
.venv/Scripts/pip install --no-deps -e .
ruff check .
mypy
pytest -q
python scripts/validate_release.py
docker compose --env-file .env.example config
docker compose --env-file .env.example build
pip-audit --no-deps -r requirements.lock --progress-spinner offLocal Docker start
Copy .env.example to .env, replace placeholders, keep X402_ENVIRONMENT=testnet and
X402_NETWORK=eip155:84532, then:
docker compose up -d --build
docker compose psContainer UID/GID: 10001:10001. No host bind-mounted writable directory is required.
This local example is intentionally testnet. Production mainnet activation requires owner approval,
a fresh PostgreSQL backup, production preflight, development bypass disabled and rollback readiness.
Documentation
Maintenance
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/maxzoa/1cent'
If you have feedback or need assistance with the MCP directory API, please join our Discord server