diariobitcoin
Registry code: 8c9c094860f59e67
DiarioBitcoin: Spanish-language crypto news (diariobitcoin.com, 2014-today), read-only, synced every minute.
- Find articles with get_news; read one with get_article (id from get_news); category slugs come from list_categories. get_full_article sells one article's full text for a few cents (USDC or USDT on Solana, x402) to agents that can pay.
- endpoint
- https://www.diariobitcoin.com/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is diariobitcoin live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is diariobitcoin free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does diariobitcoin have?
- 5 tools: list_categories, get_full_article, get_article, get_usage_guide, get_news.
- Is diariobitcoin safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 5 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_usage_guide open 2h ago
How to use this server well: recipes (today's news on a topic, latest news, topic research, paging), what each result field means, the paid-placement labels, how to cite, and what to do on each error code. Markdown. Call it once before a non-trivial task; the same text is the resource dbtc://guide.
{ "type": "object", "properties": {} }arguments 4 linesget_news open 2h ago
Search or list DiarioBitcoin articles (Spanish-language crypto news, 2014-today). With query: best matches first (relevance, boosted by recency); every word must match; write queries in Spanish ("regulación", not "regulation"; accents optional; tickers and names like BTC, ETF, BlackRock as-is). Without query: newest first. Filters: category (slug from list_categories, includes subcategories) and since (ISO date or date-time). Up to 25 items per page; page with next_cursor (a query pages through its top 200 matches, a listing through its newest 500: narrow with since or category beyond). Items carry title, url, dates (ISO UTC), author, category slugs, excerpt and the paid-placement label: paid_placement=true means sponsored or third-party content, never DiarioBitcoin's reporting. Use get_article for one article.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "limit": { "type": [ "integer", "null" ], "format": "uint32", "maximum": 25, "minimum": 1, "description": "Items per page (1-25, default 10)." }, "query": { "type": [ "string", "null" ], "maxLength": 200, "description": "Search words. The corpus is Spanish: write queries in Spanish\n(\"regulación\", not \"regulation\"); tickers and names (BTC, ETF,\nBlackRock) work as-is. Every word must match. Omit to list the newest\narticles." }, "since": { "type": [ "string", "null" ], "description": "Only articles published at or after this time: an ISO 8601 date\n(\"2026-10-27\", midnight UTC) or date-time (\"2026-10-27T09:00:00Z\")." }, "cursor": { "type": [ "string", "null" ], "description": "`next_cursor` of the previous page, with the same query, category\nand since." }, "category": { "type": [ "string", "null" ], "description": "Category slug from `list_categories` (e.g. \"mercados\"); includes its\nsubcategories." } }, "additionalProperties": false }arguments 46 lineslist_categories unknown never probed
List DiarioBitcoin's news categories: id, slug, name (Spanish), count of published articles, parent id (0 = top level) and paid_placement ("sponsored_article", "press_release" or null for editorial categories). Use a slug as get_news's category. Synced from the site hourly; as_of is the sync time.
{ "type": "object", "properties": {} }arguments 4 linesget_full_article unknown never probed
PAID: the full text of one DiarioBitcoin article, for a few cents in USDC or USDT on Solana mainnet, paid per call with x402 (no account or API key). Same arguments as get_article. Without payment it returns an x402 PaymentRequired (isError=true; accepts lists amount in atomic units, asset mint, payTo and extra.feePayer, which pays the network fee). Pay by calling again with a PaymentPayload in _meta["x402/payment"] (scheme exact: a transaction with SetComputeUnitLimit, SetComputeUnitPrice, one TransferChecked to payTo's token account, then one Memo whose data is extra.memo and nothing else, signed by your wallet, extra.feePayer as fee payer). The result is the get_article envelope with body_kind="full" and the receipt in _meta["x402/payment-response"]. Sponsored articles and press releases are not sold. Cannot pay? Use get_article (excerpt and link).
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "id": { "type": [ "integer", "null" ], "format": "uint64", "minimum": 0, "description": "Article id (the `id` of a `get_news` item)." }, "slug": { "type": [ "string", "null" ], "maxLength": 200, "description": "Article slug (the `slug` of a `get_news` item; never a URL)." } }, "additionalProperties": false }arguments 24 linesget_article unknown 2h ago
One DiarioBitcoin article by id or slug (from get_news; never a URL). Returns the get_news fields plus body as plain text. body_kind="excerpt" means the full text is not offered for this article: summarize from the excerpt and link to url, or buy the full text with get_full_article if you can pay. Sponsored articles and press releases (paid_placement=true) are always excerpt-only and must be labelled as paid or third-party content.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "id": { "type": [ "integer", "null" ], "format": "uint64", "minimum": 0, "description": "Article id (the `id` of a `get_news` item)." }, "slug": { "type": [ "string", "null" ], "maxLength": 200, "description": "Article slug (the `slug` of a `get_news` item; never a URL)." } }, "additionalProperties": false }arguments 24 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id8c9c094860f59e67.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/8c9c094860f59e67/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/8c9c094860f59e67?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.