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

mcp-operation-risk

https://87-106-119-237.sslip.io

Registry code: e49ca86a389a6c62

api record

Operation-level risk guidance for consolidated MCP tools, including schema drift and retry signals.

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

endpoint
https://87-106-119-237.sslip.io/mcp-operation-risk/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 mcp-operation-risk live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is mcp-operation-risk free to use?
Yes — the hub reached it with no key and no payment.
What tools does mcp-operation-risk have?
2 tools: evaluate_operation_risk, describe_operation_risk_service.
Is mcp-operation-risk 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
110ms

last good check

priced tools
0

of 2 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, 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 stands behind 3 doors on this origin, so the chain figures are the operator's. 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
4

distinct

settlements
18

last 2026-10-09

received on chain
0.063 USDC

concentrated

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

  • describe_operation_risk_service open 1h ago

    Check whether the actual operation inside an MCP tool call is safe before execution. Use this when one MCP tool exposes multiple operations with different side effects, so whole-tool permissions are too coarse. Provide the native MCP server identity, the tool's tools/list metadata and the intended arguments. For supported consolidated tools, distinguish read, create/add, update/mutate and delete/destructive operations. Return ALLOW, DENY, or REQUIRE_APPROVAL. Unknown, unsupported, ambiguous, or schema-changed calls fail closed with REQUIRE_APPROVAL. The evaluator never executes the source operation.

    mcp-tool

    {
  "type": "object",
  "title": "describe_operation_risk_serviceArguments",
  "properties": {}
}
    arguments 5 lines
  • evaluate_operation_risk unknown 1h ago

    Check whether the actual operation inside an MCP tool call is safe before execution. Use this when one MCP tool exposes multiple operations with different side effects, so whole-tool permissions are too coarse. Provide the native MCP server identity, the tool's tools/list metadata and the intended arguments. For supported consolidated tools, distinguish read, create/add, update/mutate and delete/destructive operations. Return ALLOW, DENY, or REQUIRE_APPROVAL. Unknown, unsupported, ambiguous, or schema-changed calls fail closed with REQUIRE_APPROVAL. The evaluator never executes the source operation.

    mcp-tool

    {
  "type": "object",
  "title": "NativeMcpEvaluationRequest",
  "required": [
    "source",
    "tool",
    "arguments"
  ],
  "properties": {
    "tool": {
      "type": "object",
      "title": "NativeToolRecord",
      "required": [
        "name",
        "description",
        "inputSchema"
      ],
      "properties": {
        "name": {
          "type": "string",
          "title": "Name",
          "description": "Exact tool name from the MCP server's tools/list response."
        },
        "_meta": {
          "anyOf": [
            {
              "type": "object",
              "additionalProperties": true
            },
            {
              "type": "null"
            }
          ],
          "title": "Meta",
          "default": null,
          "description": "Relevant tool metadata from tools/list, when present."
        },
        "icons": {
          "anyOf": [
            {
              "type": "array",
              "items": {
                "type": "object",
                "additionalProperties": true
              }
            },
            {
              "type": "null"
            }
          ],
          "title": "Icons",
          "default": null,
          "description": "Tool icons from tools/list, when present."
        },
        "title": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Title",
          "default": null,
          "description": "Tool title from tools/list, when provided by the server."
        },
        "execution": {
          "anyOf": [
            {
              "type": "object",
              "additionalProperties": true
            },
            {
              "type": "null"
            }
          ],
          "title": "Execution",
          "default": null,
          "description": "Tool execution metadata from tools/list, when present."
        },
        "annotations": {
          "type": "object",
          "title": "Annotations",
          "description": "Tool annotations from tools/list, such as read-only or destructive hints; use an empty object when absent.",
          "additionalProperties": true
        },
        "description": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Description",
          "description": "Tool description from tools/list, or null if the server omitted it."
        },
        "inputSchema": {
          "type": "object",
          "title": "Inputschema",
          "description": "Complete inputSchema from tools/list; used to validate the intended arguments and match a supported tool manifest.",
          "additionalProperties": true
        },
        "outputSchema": {
          "anyOf": [
            {
              "type": "object",
              "additionalProperties": true
            },
            {
              "type": "null"
            }
          ],
          "title": "Outputschema",
          "default": null,
          "description": "Tool output schema from tools/list, when present."
        }
      },
      "description": "The complete relevant Tool record returned by the source server's tools/list.",
      "additionalProperties": false
    },
    "source": {
      "type": "object",
      "title": "NativeSource",
      "required": [
        "server",
        "protocol_version"
      ],
      "properties": {
        "server": {
          "type": "object",
          "title": "NativeServerIdentity",
          "required": [
            "name",
            "version"
          ],
          "properties": {
            "name": {
              "type": "string",
              "title": "Name",
              "description": "Name reported by the MCP server during initialize; used as a supported-manifest lookup hint."
            },
            "version": {
              "anyOf": [
                {
                  "type": "string"
                },
                {
                  "type": "null"
                }
              ],
              "title": "Version",
              "description": "Server version reported during initialize, or null when unavailable."
            }
          },
          "description": "MCP server identity from the connection's initialize response.",
          "additionalProperties": false
        },
        "protocol_version": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Protocol Version",
          "description": "Negotiated MCP protocol version, or null when unavailable."
        }
      },
      "description": "MCP server and negotiated protocol identity for the source tool.",
      "additionalProperties": false
    },
    "arguments": {
      "type": "object",
      "title": "Arguments",
      "description": "Arguments intended for the source MCP tools/call request being evaluated. The evaluator does not execute that call.",
      "additionalProperties": true
    }
  },
  "additionalProperties": false
}
    arguments 185 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 e49ca86a389a6c62.

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

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 sslip.io 31 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.

23 more sit on this domain. All of them.