CriptoNous
REMOTE · APP.CRIPTONOUS.COM
Crypto market intelligence for AI agents: sentiment, flow, Oracle readings. x402. NFA.
Available components
Last scanned (22 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 476 tokens (~59/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage73
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 18% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://app.criptonous.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.criptonous.com | CN=YE1,O=Let's Encrypt,C=US | 3 Sept 2026 | 2 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6c2bcb7d1d5ad704f8ee03d1cb64ffab7bb |
| SANs: app.criptonous.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of app.criptonous.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| criptonous.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; form-action 'self'; img-src 'self' data: https: blob:; font-src 'self' data: https:; style-src 'self' 'unsafe-inline' https:; script-src 'self' 'unsafe-inline' 'unsafe-eval'; connect-src 'self' https: wss: ws:; worker-src 'self' blob:; frame-src 'self' https://dexscreener.com |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.criptonous.com/mcp | Verified | 200 | |
| http (plaintext) | http://app.criptonous.com/mcp | HTTPS enforced | 301 | https://app.criptonous.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
temple_budget Spending budget ~31
Consulta el tab de gasto del agent (cap diario, cap por tx, remaining, allowlist). NFA.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
temple_catalog CriptoNous catalog ~33
Devuelve el catálogo canónico del Templo Cripto Nous (SKUs, precios USDC, NFA). Público.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
temple_consume_pass Get market reading (uses AccessPass) ~82
Consume un uso del AccessPass y devuelve la lectura de los dioses (sin nuevo pago). Emite Receipt. Si las fuentes no responden devuelve fulfillment_failed y NO consume el uso.
| Name | Type | Req | Description |
|---|---|---|---|
| passId | string | yes | – |
| sku | string | yes | – |
| symbol | string | – | Token a analizar (ej. SOL, BTC). Default SOL. |
No output schema declared.
No examples provided.
temple_get_receipt Get receipt ~48
Obtiene un Receipt élite por receiptId (JSON, NFA 6 idiomas, HMAC v2). No es DTE/SII.
| Name | Type | Req | Description |
|---|---|---|---|
| receiptId | string | yes | – |
No output schema declared.
No examples provided.
temple_list_receipts List receipts ~28
Lista receipts del agent autenticado (más recientes primero).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
No output schema declared.
No examples provided.
temple_request_tribute Request x402 payment ~58
Prepara TributeRequest (SPL USDC Solana). Requiere API key. Tras verify se emite AccessPass reutilizable.
| Name | Type | Req | Description |
|---|---|---|---|
| sku | string | yes | SKU (ej. hermes.pulse o session.24h) |
No output schema declared.
No examples provided.
temple_validate_pass Validate AccessPass ~44
Valida AccessPass vigente (sin consumir). Opcional: sku a comprobar contra allowedSkus.
| Name | Type | Req | Description |
|---|---|---|---|
| passId | string | yes | – |
| sku | string | – | – |
No output schema declared.
No examples provided.
temple_verify Verify payment and issue AccessPass ~61
Verifica SPL USDC y emite AccessGrant + AccessPass. Idempotente: reintenta verify, no pagues dos veces.
| Name | Type | Req | Description |
|---|---|---|---|
| payerWallet | string | yes | – |
| requestId | string | yes | – |
| txSignature | string | yes | – |
No output schema declared.
No examples provided.
How do I install the CriptoNous MCP server?
CriptoNous is a hosted endpoint at https://app.criptonous.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · app.criptonous.com
claude mcp add --transport http com-criptonous-app-market-intelligence 'https://app.criptonous.com/mcp'
What is the CriptoNous MCP server?
CriptoNous is an MCP server listed in the public MCP registry as com.criptonous.app/market-intelligence. Crypto market intelligence for AI agents: sentiment, flow, Oracle readings. x402. NFA. This page covers its hosted endpoint (https://app.criptonous.com/mcp).
Is the CriptoNous MCP server safe to use?
CriptoNous scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the CriptoNous MCP server expose?
CriptoNous exposes 8 tools: temple_catalog, temple_request_tribute, temple_verify, temple_validate_pass, temple_consume_pass, and 3 more. Their descriptions and schemas cost roughly 385 tokens of context every time the server is loaded.
Does the CriptoNous MCP server require authentication?
No. We connected to CriptoNous without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CriptoNous MCP server still maintained?
CriptoNous is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.