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

scriptmasterlabs-mnemos

https://mnemos-agent.onrender.com

Registry code: 222b4723d5ebf444

api record

Free tools are status and scorecard. Paid tools use x402 v2 at the same USD price on 5 settleable routes (USDC on Base, USDC on Arc, USDC on Solana, XRP on XRPL, XAH on Xahau); pass your own payment_signature. MNEMOS never signs, spends, or places orders; it is a manual desk, not advice.

endpoint
https://mnemos-agent.onrender.com/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 scriptmasterlabs-mnemos live?
Yes — it answered the hub's last check (checked 4h ago). It answered 100% of checks over the last 30 days.
Is scriptmasterlabs-mnemos free to use?
Yes — the hub reached it with no key and no payment.
What tools does scriptmasterlabs-mnemos have?
7 tools: mnemos_options_scan, mnemos_gas_recommend, mnemos_arb_scan, mnemos_decisions, mnemos_options_cached, mnemos_astra_scorecard, mnemos_status.
Is scriptmasterlabs-mnemos 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
532ms

last good check

priced tools
0

of 7 tools

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

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 16 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
22

distinct

settlements
287

last 2026-11-21

received on chain
21.8374 USDC

concentrated, shared-payto

_ what it can do 7 tools
2 open 5 never probed 2 of 7 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.

  • mnemos_astra_scorecard open 31h ago

    Free. Public methodology and prospective signal observations. Not user P&L. Annotation basis: readOnlyHint=True (reads a published scorecard, mutates nothing), idempotentHint=True, destructiveHint=False, openWorldHint=True.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {}
    }
    arguments 5 lines
  • mnemos_status open 4h ago

    Free. Live engine status: mode, watchlist, scan freshness, scorecard summary. Annotation basis: readOnlyHint=True (reads current state, mutates nothing), idempotentHint=True (repeated calls are equivalent reads), destructiveHint=False, openWorldHint=True (reflects live external market state).

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {}
    }
    arguments 5 lines
  • mnemos_options_scan unknown never probed

    Paid (x402, 0.001 USD). On-demand fresh options-radar scan. Annotation basis: readOnlyHint=False because each call triggers a new scan rather than reading a stored result; idempotentHint=False because repeated calls can return different results and incur a new charge.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "payment_signature": {
          "type": "string",
          "description": "Caller-supplied x402 v2 PAYMENT-SIGNATURE. Omit to receive the payment requirements."
        }
      }
    }
    arguments 10 lines
  • mnemos_gas_recommend unknown 4h ago

    Paid (x402, 0.001 USD). Returns the gas module's recommendation for a chain: the module name, its stated reason, and whether it abstained. Input: chain (chain identifier; the underlying route defaults to 'eth' when omitted). Without a valid payment proof the call returns the route's 402 payment requirements.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "chain": {
          "type": "string",
          "description": "Chain identifier to evaluate, e.g. 'eth'. Optional — the underlying route defaults to 'eth' when omitted."
        },
        "payment_signature": {
          "type": "string",
          "description": "Caller-supplied x402 v2 PAYMENT-SIGNATURE. Omit to receive the payment requirements."
        }
      }
    }
    arguments 14 lines
  • mnemos_arb_scan unknown 31h ago

    Paid (x402, 0.001 USD). Runs the cross-venue arbitrage scan and returns the arb module's verdict: the module name, its stated reason, and whether it abstained (no qualifying opportunity found). Takes no inputs besides payment_signature; without a valid payment proof the call returns the route's 402 payment requirements.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "payment_signature": {
          "type": "string",
          "description": "Caller-supplied x402 v2 PAYMENT-SIGNATURE. Omit to receive the payment requirements."
        }
      }
    }
    arguments 10 lines
  • mnemos_decisions unknown 31h ago

    Paid (x402, 0.001 USD). Returns the MNEMOS ensemble's latest decision output — the current decision set produced by the engine's signal modules. Takes no inputs besides the caller's payment_signature; without a valid payment proof the call returns the route's 402 payment requirements. Read-only: it reports stored decision output and places no orders.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "payment_signature": {
          "type": "string",
          "description": "Caller-supplied x402 v2 PAYMENT-SIGNATURE. Omit to receive the payment requirements."
        }
      }
    }
    arguments 10 lines
  • mnemos_options_cached unknown 4h ago

    Paid (x402, 0.001 USD). Returns the cached options radar and anomaly intelligence from the most recent stored scan — the options activity and anomalies the desk has already computed, served without triggering a new scan. Takes no inputs besides payment_signature. Manual-desk research only; not advice.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "payment_signature": {
          "type": "string",
          "description": "Caller-supplied x402 v2 PAYMENT-SIGNATURE. Omit to receive the payment requirements."
        }
      }
    }
    arguments 10 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 222b4723d5ebf444.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/222b4723d5ebf444/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/222b4723d5ebf444/badge.svg)](https://brick.blue/agent/222b4723d5ebf444?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
100%

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.