_ registry / mcp http-sse · checked 33m ago

masaq-audit

https://mcp-relay.tail304f3.ts.net

Registry code: b6a76f5024cb1995

api record

Declared as an MCP endpoint by 8004scan; probed directly.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp-relay.tail304f3.ts.net/mcp
protocol
http-sse ·2025-06-18
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 masaq-audit live?
Yes — it answered the hub's last check (checked 33m ago). It answered 100% of checks over the last 30 days.
Is masaq-audit free to use?
Yes — the hub reached it with no key and no payment.
What tools does masaq-audit have?
9 tools: get_vectors, get_danger_map, audit_prep, get_static_analysis, get_source, get_prep_summary, audit_execute, audit_quote, ….
Is masaq-audit 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
319ms

last good check

priced tools
0

of 9 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 9 tools
9 never probed 0 of 9 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.

  • get_vectors unknown never probed

    Returns triaged attack vectors relevant to this codebase.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "audit_name"
  ],
  "properties": {
    "audit_name": {
      "type": "string",
      "description": "Audit name from audit_prep"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • get_danger_map unknown 33m ago

    Returns pre-extracted hotspots from a completed prep.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "audit_name"
  ],
  "properties": {
    "audit_name": {
      "type": "string",
      "description": "Audit name from audit_prep"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • audit_prep unknown never probed

    Run the full prep pipeline on a repository via Server A. Clones the repo, runs static analysis (Slither, Aderyn, Forge), extracts attack vectors, builds danger map, and segments the codebase. No LLM calls -- deterministic and free.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "repo_url",
    "audit_name"
  ],
  "properties": {
    "scope": {
      "type": "string",
      "default": "",
      "description": "Comma-separated list of in-scope file paths"
    },
    "contest": {
      "type": "string",
      "default": "",
      "description": "Contest type: agentarena, sherlock, code4rena, etc."
    },
    "repo_url": {
      "type": "string",
      "format": "uri",
      "description": "Git repository URL to audit"
    },
    "audit_name": {
      "type": "string",
      "pattern": "^[a-zA-Z0-9._-]+$",
      "description": "Short name for this audit (used in paths)"
    }
  },
  "additionalProperties": false
}
    arguments 31 lines
  • get_static_analysis unknown never probed

    Returns Slither/Aderyn findings and test results.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "audit_name"
  ],
  "properties": {
    "audit_name": {
      "type": "string",
      "description": "Audit name from audit_prep"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • get_source unknown never probed

    Returns concatenated source code for in-scope files.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "audit_name"
  ],
  "properties": {
    "audit_name": {
      "type": "string",
      "description": "Audit name from audit_prep"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • get_prep_summary unknown never probed

    Returns the audit prep summary: nSLOC, strategy, segment plan, manifest.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "audit_name"
  ],
  "properties": {
    "audit_name": {
      "type": "string",
      "description": "Audit name from audit_prep"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • audit_execute unknown never probed

    Run a full security audit (stages 2-4: analysis, variant analysis, validation). REQUIRES x402 PAYMENT. Call audit_quote first to get the price and payment requirements. Pass the base64-encoded x402 payment payload as the payment_payload parameter. The payment will be verified before the audit starts, and settled after findings are delivered.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "audit_name",
    "payment_payload"
  ],
  "properties": {
    "audit_name": {
      "type": "string",
      "pattern": "^[a-zA-Z0-9._-]+$",
      "description": "Audit name from a completed audit_prep and audit_quote"
    },
    "payment_payload": {
      "type": "string",
      "description": "Base64-encoded x402 payment payload from the paying client"
    },
    "timeout_per_stage": {
      "type": "integer",
      "default": 1200,
      "description": "Timeout per stage in seconds (default 1200)"
    }
  },
  "additionalProperties": false
}
    arguments 25 lines
  • audit_quote unknown 33m ago

    Returns a price quote for a full security audit. Requires a completed prep (run audit_prep first). Returns nSLOC count, estimated price in USDC, and x402 payment requirements that a client needs to construct payment. This tool is FREE.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "audit_name"
  ],
  "properties": {
    "audit_name": {
      "type": "string",
      "pattern": "^[a-zA-Z0-9._-]+$",
      "description": "Audit name from a completed audit_prep"
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • get_findings unknown 33m ago

    Returns all findings markdown files from a completed audit.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "audit_name"
  ],
  "properties": {
    "audit_name": {
      "type": "string",
      "description": "Audit name from audit_prep"
    }
  },
  "additionalProperties": false
}
    arguments 14 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 b6a76f5024cb1995.

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

_ also on ts.net 8 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.