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.

MorseByte x402 Edge Data Refinery & Quant Gateway

REMOTE · API.MORSEBYTE.CO.ZA · 2 COMPONENTS

Web data refinery, link verifier, AI JSON extractor, and quant regime classifier via HTTP 402.

65 Trust /100

Last scanned (22 hours ago)

Scores higher than 48% of remote servers

Reachable. Last reached 24 Oct 2026.

Category Web Scraping

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 Security63
Transport & Reachability100
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 495 tokens (~55/item across 9 items; 8 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: schema churn in the 5 days we've observed: 0 tool removals, 4 breaking changes, 0 auth/transport breaks, 4 additions. See how to fix → Fail
Tool Coverage89
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 67% 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
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 22 Oct 26 −1
    • Tool “morsebyte_quant_regime” rewrote its description, which is the text the model reads security
    • Tool coverage: 100% → 67% ▼ functional
    • Server version: 1.2.0 → 1.3.1 functional
    • “morsebyte_extract_json” added an optional parameter “schema” cosmetic
    • “morsebyte_llm_router” added an optional parameter “system” cosmetic
    • “morsebyte_dom_snapshot” reworded the description of “url” cosmetic
    • “morsebyte_ephemeral_store” reworded the description of “data” cosmetic
    • “morsebyte_ephemeral_store” reworded the description of “ttl_seconds” cosmetic
    • “morsebyte_extract_json” reworded the description of “prompt” cosmetic
    • “morsebyte_llm_router” reworded the description of “prompt” cosmetic
    • “morsebyte_verify_links” reworded the description of “urls” cosmetic
    • “morsebyte_quant_regime” reworded the description of “closes” cosmetic
    • “morsebyte_quant_regime” reworded the description of “symbol” cosmetic
    • “morsebyte_quant_regime” reworded the description of “timeframe” cosmetic
    • “morsebyte_refine_url” reworded the description of “url” cosmetic
    • “morsebyte_llm_router” reworded the description of “tier” cosmetic
    • “morsebyte_content_digest” reworded the description of “urls” cosmetic
  • 20 Oct 26 +1
    • Stability: unverified → fail ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • The server changed its declared name: morsebyte-x402-mcp → io.github.Ceejaythenerd/morsebyte-x402-mcp security
    • Tool “morsebyte_extract_json” rewrote its description, which is the text the model reads security
    • Tool “morsebyte_quant_regime” rewrote its description, which is the text the model reads security
    • Tool “morsebyte_refine_url” rewrote its description, which is the text the model reads security
    • Tool “morsebyte_verify_links” rewrote its description, which is the text the model reads security
    • Prompt “analyze_market_regime” was removed ▼ functional
    • Prompt “audit_research_citations” was removed ▼ functional
    • Resource “MorseByte LLM Discovery Guide” was removed ▼ functional
    • Resource “MorseByte x402 Pricing Schedule” was removed ▼ functional
    • Tool “morsebyte_extract_json” dropped its output schema ▼ functional
    • Tool “morsebyte_quant_regime” dropped its output schema ▼ functional
    • Tool “morsebyte_refine_url” dropped its output schema ▼ functional
    • Tool “morsebyte_verify_links” dropped its output schema ▼ functional
    • Schema quality: 73 → 60 ▲ functional
    • New prompt “audit_and_digest_sources” functional
    • MCP protocol version: 2025-03-26 → 2025-06-18 functional
    • New resource “MorseByte x402 Pricing & Wallet Manifest” functional
    • Server version: 1.3.0 → 1.2.0 functional
    • New tool “morsebyte_dom_snapshot” functional
    • New tool “morsebyte_content_digest” functional
    • New tool “morsebyte_ephemeral_store” functional
    • New tool “morsebyte_llm_router” functional
    • “morsebyte_quant_regime” added an optional parameter “timeframe” cosmetic
    • “morsebyte_extract_json” reworded the description of “prompt” cosmetic
    • “morsebyte_extract_json” reworded the description of “url” cosmetic
    • “morsebyte_quant_regime” reworded the description of “closes” cosmetic
    • “morsebyte_quant_regime” reworded the description of “symbol” cosmetic
    • “morsebyte_refine_url” reworded the description of “url” cosmetic
    • “morsebyte_verify_links” reworded the description of “urls” cosmetic
  • 19 Oct 26 65

    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 24 Oct 2026 · Probed https://api.morsebyte.co.za/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=morsebyte.co.za CN=WE1,O=Google Trust Services,C=US 15 Oct 2026 13 Jan 2027 ECDSA 256 ECDSA-SHA256 ed1956af7ac29e18131431824fe855d0
SANs: morsebyte.co.za, api.morsebyte.co.za, *.api.morsebyte.co.za
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 api.morsebyte.co.za. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
za. present 45749 8 Verified
co.za. present 41369 8 Verified
morsebyte.co.za. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.morsebyte.co.za/mcp Verified 200
http (plaintext) http://api.morsebyte.co.za/mcp Served over HTTP 200
MCP tools · 8 exposed · ~468 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
morsebyte_content_digest ~52

Scrape up to 5 URLs in parallel and summarize each into 3 bullet points ($0.010 USDC via x402).

NameTypeReqDescription
urlsarrayyes1 to 5 public URLs

No output schema declared.

No examples provided.

morsebyte_dom_snapshot ~42

Inspect webpage headings, interactive counts, and link tree ($0.025 USDC via x402).

NameTypeReqDescription
urlstringyesPublic URL to inspect

No output schema declared.

No examples provided.

morsebyte_ephemeral_store ~61

Store temporary JSON state in Cloudflare Edge KV with custom TTL ($0.001 USDC via x402).

NameTypeReqDescription
dataobjectyesJSON state to store
ttl_secondsnumber–TTL in seconds (60-86400)

No output schema declared.

No examples provided.

morsebyte_extract_json ~71

Scrape a URL and extract structured JSON matching a prompt via Llama 3.3 70B ($0.030 USDC via x402).

NameTypeReqDescription
promptstringyesExtraction instructions
schemaobject–Optional JSON schema
urlstringyesTarget webpage URL

No output schema declared.

No examples provided.

morsebyte_llm_router ~70

Route prompts to fast edge models (Llama 3.1 8B or Llama 3.3 70B) ($0.002 USDC via x402).

NameTypeReqDescription
promptstringyes–
systemstring––
tierstring––

No output schema declared.

No examples provided.

morsebyte_quant_regime ~71

Compute RSI-14, EMA-20/50, volatility, lag-1 autocorrelation, and market regime ($0.050 USDC via x402).

NameTypeReqDescription
closesarrayyesAt least 10 closing prices
symbolstring––
timeframestring––

No output schema declared.

No examples provided.

morsebyte_refine_url ~49

Fetch any public URL and extract clean, token-efficient prose ($0.015 USDC via x402).

NameTypeReqDescription
urlstringyesPublic HTTP/HTTPS URL to scrape and refine

No output schema declared.

No examples provided.

morsebyte_verify_links ~52

Verify up to 20 URLs in parallel for HTTP status, liveness, and latency ($0.005 USDC via x402).

NameTypeReqDescription
urlsarrayyes1 to 20 public URLs

No output schema declared.

No examples provided.

Install

How do I install the MorseByte x402 Edge Data Refinery & Quant Gateway MCP server?

MorseByte x402 Edge Data Refinery & Quant Gateway is a hosted endpoint at https://api.morsebyte.co.za/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 · api.morsebyte.co.za

# add to Claude Code
claude mcp add --transport http ceejaythenerd-morsebyte-x402-mcp 'https://api.morsebyte.co.za/mcp'
Common questions

What is the MorseByte x402 Edge Data Refinery & Quant Gateway MCP server?

MorseByte x402 Edge Data Refinery & Quant Gateway is an MCP server listed in the public MCP registry as io.github.Ceejaythenerd/morsebyte-x402-mcp. Web data refinery, link verifier, AI JSON extractor, and quant regime classifier via HTTP 402. This page covers its hosted endpoint (https://api.morsebyte.co.za/mcp).

Is the MorseByte x402 Edge Data Refinery & Quant Gateway MCP server safe to use?

MorseByte x402 Edge Data Refinery & Quant Gateway scores 65 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 MorseByte x402 Edge Data Refinery & Quant Gateway MCP server expose?

MorseByte x402 Edge Data Refinery & Quant Gateway exposes 8 tools: morsebyte_refine_url, morsebyte_verify_links, morsebyte_extract_json, morsebyte_quant_regime, morsebyte_ephemeral_store, and 3 more. Their descriptions and schemas cost roughly 468 tokens of context every time the server is loaded.

Does the MorseByte x402 Edge Data Refinery & Quant Gateway MCP server require authentication?

No. We connected to MorseByte x402 Edge Data Refinery & Quant Gateway without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the MorseByte x402 Edge Data Refinery & Quant Gateway MCP server still maintained?

MorseByte x402 Edge Data Refinery & Quant Gateway is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.