_ registry / mcp streamable-http · checked 2m ago

Dredd MCP — Pre-Flight Security

https://analytics.dugganusa.com

Registry code: 1e6fcd86a47dc209

api record

Dredd judges MCP server invocations BEFORE damage — server identity AND dependency graph (npm/pypi). check_mcp_server takes a server name (and optional version + tool) and returns a signed verdict: BLOCK, ADVISORY, REVIEW or ALLOW. The dep_graph field in the response tells you whether transitive supply-chain risk (Shai-Hulud class) was checked.

endpoint
https://analytics.dugganusa.com/api/v1/dredd/mcp
protocol
streamable-http ·2024-11-05
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 Dredd MCP — Pre-Flight Security live?
Yes — it answered the hub's last check (checked 2m ago). It answered 100% of checks over the last 30 days.
Is Dredd MCP — Pre-Flight Security free to use?
Yes — the hub reached it with no key and no payment.
What tools does Dredd MCP — Pre-Flight Security have?
1 tool: check_mcp_server.
Is Dredd MCP — Pre-Flight Security 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 99.6%· all time 99.6%

latency
482ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 280 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • check an mcp server before invoking it
  • check an mcp server's dependency supply chain risk
takes → gives
text → data
tools
1 reads
_ 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 1 tools
1 never probed 0 of 1 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.

  • check_mcp_server reads unknown 7h ago

    Pre-flight security verdict for an MCP server invocation. Judges BOTH server-level reputation AND the server's dependency graph (npm/pypi) against the DugganUSA threat-intel corpus (1.13M+ IOCs, Shai-Hulud + typosquat + LOLBin families). Returns BLOCK / ADVISORY / REVIEW / ALLOW with severity, evidence, dep-graph summary, and HMAC-signed response. REVIEW means we hold NO RECORD of this server -- not that it is safe. A brand-new attacker-published server also looks like this, so REVIEW calls for a look, not a pass. ALLOW is only returned when we actually resolved the server and scanned its dependency graph; known_to_us and dep_graph.scanned confirm it. Suited to a pre-flight check before a tool on another MCP server is used, especially one from outside the official MCP Registry.

    mcp-tool

    {
      "type": "object",
      "required": [
        "server"
      ],
      "properties": {
        "tool": {
          "type": "string",
          "description": "Optional name of the specific tool being invoked"
        },
        "server": {
          "type": "string",
          "minLength": 1,
          "description": "REQUIRED. The server to judge: its exact MCP Registry name (io.github.owner/server-name, optionally @version). A bare name (server-name) is judged as typed, never mapped to a registry server, and the matching full names come back in input.did_you_mean. Also resolved, only when the identity is provable: a registry URL (https://registry.modelcontextprotocol.io/v0/servers/<name>) and a GitHub repo (\"owner/repo\" or https://github.com/owner/repo) published by that owner as exactly one registry server. Package names (npm/PyPI), images and Smithery ids are recorded but judged as given (usually REVIEW): their name does not prove which code runs. Refused: commands, shell metacharacters, non-ASCII, local paths, endpoint URLs. No substring or fuzzy matching: anything we cannot resolve to exactly one server returns REVIEW, never a guess."
        },
        "version": {
          "type": "string",
          "description": "Optional version of the MCP server (semver). A version inside `server` ([email protected]) is used when this is empty."
        }
      },
      "additionalProperties": true
    }
    arguments 22 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 1e6fcd86a47dc209.

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

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.