prg-risk-mcp
https://prg-risk-mcp-production.up.railway.app
Registry code: c1312e503461c849
Market regime, 7-dimension risk vectors and payment hazard grades. Abstains when data is thin.
from a public catalogue that lists it, not from the operator
- endpoint
- https://prg-risk-mcp-production.up.railway.app/mcp
- protocol
- streamable-http ·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 prg-risk-mcp live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is prg-risk-mcp free to use?
- Partly — some of its tools are open, others need a key or payment.
- What tools does prg-risk-mcp have?
- 5 tools: get_mhi, get_regime, check_counterparty, get_alerts, get_risk_snapshot.
- Is prg-risk-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.
90 days 100%· all time 100%
last good check
of 5 tools
- degraded → live
- unknown → live
- topic
- finance & markets
- used for
- get market risk regime
- get risk score vector for an asset
- grade hazard of a payment endpoint
- pre-audit a paid endpoint before buying
- takes → gives
- text → data
- tools
- 5 reads
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.
through this hub
successful
what callers paid
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_counterparty reads 0.5 USDC paid 12h ago
Pre-audit a payment-gated endpoint before you buy from it. Two tiers, neither of which pays the endpoint: a live unpaid probe (challenge parse, scheme, latency, per-probe pass/fail, endpoint grade), and the on-chain settlement history of the offer's payee (has this address ever actually collected, how recently, how often). [paid: $0.50 USDC on Base]
{ "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "http(s) URL to probe." } }, "additionalProperties": false }arguments 13 linesget_alerts reads 0.02 USDC paid 1h ago
Open PRG risk alert records, optionally filtered to those newer than a timestamp. [paid: $0.02 USDC on Base]
{ "type": "object", "properties": { "asset": { "enum": [ "BTC", "STBL", "WTI", "EQ", "CREDIT", "PRG" ], "type": "string" }, "since": { "type": "string", "description": "ISO-8601 timestamp." } }, "additionalProperties": false }arguments 21 linesget_risk_snapshot reads 0.05 USDC paid 1h ago
PRG composite risk score plus the seven dimension-level scores (INT, FRG, PRE, THR, PRO, REC, VAL) for one instrument or the market. [paid: $0.05 USDC on Base]
{ "type": "object", "properties": { "asset": { "enum": [ "BTC", "STBL", "WTI", "EQ", "CREDIT", "PRG" ], "type": "string", "description": "Omit for market-wide." } }, "additionalProperties": false }arguments 18 linesget_regime reads open 1h ago
Current PRG market risk regime label and composite score band. Free, rate-limited. [free] (free tier, rate-limited per IP)
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesget_mhi reads unknown 12h ago
Machine Hazard Index reading for a payment rail, facilitator, or endpoint, with component letter-grades and abstention status. [free] (free while the MHI methodology stamps its output pre-calibration; moves to $0.05 on a calibrated release (SPEC §5.3))
{ "type": "object", "required": [ "scope", "id" ], "properties": { "id": { "type": "string", "minLength": 1 }, "scope": { "enum": [ "rail", "facilitator", "endpoint" ], "type": "string" } }, "additionalProperties": false }arguments 22 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idc1312e503461c849.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/c1312e503461c849/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/c1312e503461c849?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.