_ registry / mcp streamable-http · checked 1h ago

morsebyte-x402-mcp

https://api.morsebyte.co.za

Registry code: 949c9cf08d71acfc

api record

Stateless web data refinery, parallel citation link verifier, Workers AI structured JSON extractor, and quantitative market regime classifier gated via HTTP 402 (USDC on Base & Stellar).

endpoint
https://api.morsebyte.co.za/mcp
protocol
streamable-http ·2025-03-26
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is morsebyte-x402-mcp live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is morsebyte-x402-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does morsebyte-x402-mcp have?
4 tools: morsebyte_verify_links, morsebyte_refine_url, morsebyte_extract_json, morsebyte_quant_regime.
Is morsebyte-x402-mcp 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.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
113ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
3 open 1 never probed 3 of 4 classified

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.

  • morsebyte_refine_url open 1h ago

    Fetch any public HTTPS URL and extract clean, token-efficient LLM-ready prose, page title, HTTP status, and character count ($0.015 USDC via HTTP 402 on Base or Stellar).

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "title": "Target URL",
          "format": "uri",
          "description": "Full public HTTPS URL to scrape and refine into clean text (e.g. https://example.com)"
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • morsebyte_extract_json open 1h ago

    Scrape any public webpage and extract a strict, deterministic JSON object matching a custom prompt or JSON Schema using Cloudflare Workers AI Llama 3.3 70B ($0.030 USDC via HTTP 402).

    mcp-tool

    {
      "type": "object",
      "required": [
        "url",
        "prompt"
      ],
      "properties": {
        "url": {
          "type": "string",
          "title": "Target Webpage URL",
          "format": "uri",
          "description": "Public HTTPS URL to scrape prior to AI JSON extraction"
        },
        "prompt": {
          "type": "string",
          "title": "Extraction Instructions",
          "description": "Detailed description of the fields, entities, or tables to extract into structured JSON"
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
  • morsebyte_quant_regime open 1h ago

    Compute RSI-14, EMA-20/50 trend structure, log-return volatility, lag-1 autocorrelation, and momentum vs. mean-reversion market regime from chronological closing prices ($0.050 USDC via HTTP 402).

    mcp-tool

    {
      "type": "object",
      "required": [
        "closes"
      ],
      "properties": {
        "closes": {
          "type": "array",
          "items": {
            "type": "number",
            "description": "Closing price for candle period"
          },
          "title": "Chronological Closing Prices",
          "maxItems": 500,
          "minItems": 30,
          "description": "Array of chronological closing prices (minimum 30 candles required for accurate EMA/RSI calculation)"
        },
        "symbol": {
          "type": "string",
          "title": "Asset Ticker Symbol",
          "description": "Optional asset ticker identifier (e.g. BTCUSD, XAUUSD, V75)"
        }
      },
      "additionalProperties": false
    }
    arguments 25 lines
  • morsebyte_verify_links unknown never probed

    Deterministically verify up to 20 URLs in parallel from the Cloudflare edge for HTTP status code, liveness, response latency, and final redirect destination ($0.005 USDC via HTTP 402).

    mcp-tool

    {
      "type": "object",
      "required": [
        "urls"
      ],
      "properties": {
        "urls": {
          "type": "array",
          "items": {
            "type": "string",
            "format": "uri",
            "description": "Public HTTPS URL to check"
          },
          "title": "URLs to Verify",
          "maxItems": 20,
          "minItems": 1,
          "description": "Array of 1 to 20 public HTTPS URLs to audit in parallel"
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 949c9cf08d71acfc.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/949c9cf08d71acfc/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/949c9cf08d71acfc/badge.svg)](https://brick.blue/agent/949c9cf08d71acfc?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.

_ how we know
card completeness
80%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.