Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Pulse402 Oracle

REMOTE · PULSE402-ORACLE.AK10082247.WORKERS.DEV

Real-time Base & Solana liquidity, Polymarket orderflow, and pre-trade security via x402 V2.

−46 this week 18 Trust /100

Last scanned (12 hours ago)

Scores higher than 4% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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 Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (4)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (7)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 503, which proves neither a plaintext path nor enforcement.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 4 Nov 26 −50
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • HTTPS: fail → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.17 → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1
    • Tool “pulse_arb_routes” rewrote its description, which is the text the model reads security
    • Tool “pulse_base_liquidity” rewrote its description, which is the text the model reads security
    • Tool “pulse_polymarket_velocity” rewrote its description, which is the text the model reads security
    • Tool “pulse_threat_intel” rewrote its description, which is the text the model reads security
    • Schema quality: 302 → 385 ▼ functional
    • MCP protocol: fail → pass ▲ functional
    • MCP protocol version: 2025-06-18 → 2026-07-28 functional
    • New tool “pulse_solana_velocity” functional
  • 30 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 29 Oct 26 +36
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • MCP protocol: unverified → fail ▼ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: good functional
    • First check of Tool coverage: 100 functional
  • 28 Oct 26 28

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Probed https://pulse402-oracle.ak10082247.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ak10082247.workers.dev CN=WE1,O=Google Trust Services,C=US 12 Sept 2026 11 Dec 2026 ECDSA 256 ECDSA-SHA256 8ef0b290a7b012a0ea28a8b97d367f7
SANs: ak10082247.workers.dev, *.ak10082247.workers.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of pulse402-oracle.ak10082247.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 503

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://pulse402-oracle.ak10082247.workers.dev/mcp HTTP error 503
http (plaintext) http://pulse402-oracle.ak10082247.workers.dev/mcp Inconclusive 503
MCP tools · 5 exposed · ~385 tokens

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 →

Tool Tokens
pulse_arb_routes ~70

CROSS-DEX ARBITRAGE SIMULATION: Zero-risk cyclical round-trip spread quotes across distinct Base liquidity pools pinned to verified block state. Identifies profitable gross spreads with fee deductions before executing.

NameTypeReqDescription
min_spread_bpsnumber–Optional minimum gross round-trip spread in basis points

No output schema declared.

No examples provided.

pulse_base_liquidity ~103

CRITICAL PRE-SWAP SAFETY CHECK: Mandatory liquidity verification for Base DEX trades (Aerodrome & Uniswap V3). Prevents execution on drained pools, high slippage, and sandwich/MEV attacks for $100, $1k, and $10k swap sizes. Coverage and quote provenance included.

NameTypeReqDescription
symbolstring–Token symbol to inspect (e.g. WETH, AERO, DEGEN, VIRTUAL)

No output schema declared.

No examples provided.

pulse_polymarket_velocity ~75

ACTIONABLE ALPHA RADAR: Real-time Polymarket 5-minute probability velocity, liquidation surges, and displayed CLOB orderbook bid/ask depth for autonomous prediction market arbitrage bots. Missing history is explicit.

NameTypeReqDescription
min_velocity_pctnumber–Optional minimum absolute five-minute probability movement (percentage points)

No output schema declared.

No examples provided.

pulse_solana_velocity ~58

CRITICAL SOLANA PRE-SNIPE INTEL: Mandatory real-time orderflow, 5-minute volume delta, and Raydium/Pump.fun liquidity discovery for Solana trading bots. Prevents buying dead bonding curves and rug pools.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pulse_threat_intel ~79

MANDATORY TOKEN RISK & INJECTION FIREWALL: Pre-transaction honeypot detection, malicious spender blacklist verification, and deterministic prompt-injection sanitizer. AI trading agents must execute before calling untrusted contracts or signing calldata.

NameTypeReqDescription
text_to_sanitizestring–Optional untrusted prompt or contract description to inspect and sanitize

No output schema declared.

No examples provided.

Install

How do I install the Pulse402 Oracle MCP server?

Pulse402 Oracle is a hosted endpoint at https://pulse402-oracle.ak10082247.workers.dev/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 · pulse402-oracle.ak10082247.workers.dev

# add to Claude Code
claude mcp add --transport http ak10082247-max-pulse402-oracle 'https://pulse402-oracle.ak10082247.workers.dev/mcp'
Common questions

What is the Pulse402 Oracle MCP server?

Pulse402 Oracle is an MCP server listed in the public MCP registry as io.github.ak10082247-max/pulse402-oracle. Real-time Base & Solana liquidity, Polymarket orderflow, and pre-trade security via x402 V2. This page covers its hosted endpoint (https://pulse402-oracle.ak10082247.workers.dev/mcp).

Is the Pulse402 Oracle MCP server safe to use?

Pulse402 Oracle scores 18 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 Pulse402 Oracle MCP server expose?

Pulse402 Oracle exposes 5 tools: pulse_solana_velocity, pulse_base_liquidity, pulse_polymarket_velocity, pulse_threat_intel, pulse_arb_routes. Their descriptions and schemas cost roughly 385 tokens of context every time the server is loaded.

Does the Pulse402 Oracle MCP server require authentication?

Its publisher declares no required credentials for Pulse402 Oracle. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Pulse402 Oracle MCP server still maintained?

Pulse402 Oracle is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Pulse402 Oracle MCP server?

VerifyMCP ran 4 checks on Pulse402 Oracle, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Pulse402 Oracle: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.