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

NPDES Permit Renewal Sentinel

https://npdes.amacunia.fr

Registry code: 3ba5e89e93458db0

api record

Renewal deadline of individual NPDES water discharge permits (33 U.S.C. 1342, 40 CFR 122.21(d)), read from the weekly ICIS-NPDES national data set published by EPA (ECHO data downloads). Use npdes_permit_example (free) to see the output; npdes_permit_lookup is paid via x402 (USDC on Base). Not affiliated with or endorsed by EPA.

endpoint
https://npdes.amacunia.fr/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 it live, free and safe measured by this hub
Is NPDES Permit Renewal Sentinel live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is NPDES Permit Renewal Sentinel free to use?
Not measured yet.
What tools does NPDES Permit Renewal Sentinel have?
2 tools: npdes_permit_example, npdes_permit_lookup.
Is NPDES Permit Renewal Sentinel 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
226ms

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 also stands behind 9 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
12

distinct

settlements
56

last 2026-11-22

received on chain
0.522 USDC

shared-payto

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

  • npdes_permit_example unknown never probed

    Free sample: a real answer, same shape as npdes_permit_lookup.

    mcp-tool

    {
      "type": "object",
      "title": "npdes_permit_exampleArguments",
      "properties": {}
    }
    arguments 5 lines
  • npdes_permit_lookup unknown never probed

    Use this when you need the renewal deadline of a US water discharge permit: for 1 to 10 NPDES permit numbers, the expiration date on file with EPA, the last day to send the renewal application (180 days before expiration, and the safe date one day earlier), whether that date binds (EPA-issued permit) or the State's own rule governs, days left, and the published status once the term has ended. Individual permits only. No facility names, no addresses. Price: 0.01 USDC per call (x402). Free trial: set free_trial to true (3 calls per day per caller).

    mcp-tool

    {
      "type": "object",
      "required": [
        "permits"
      ],
      "properties": {
        "permits": {
          "type": "string",
          "pattern": "^[A-Za-z0-9]{9}( *, *[A-Za-z0-9]{9}){0,9}$",
          "description": "1 to 10 NPDES permit numbers (9 ASCII letters or digits each, for example NH0100013), comma-separated"
        },
        "free_trial": {
          "type": "boolean",
          "description": "Set to true to ask for the free trial (3 calls per day per caller, shared with the web route, within a daily cap for the service). Without it, the tool asks for an x402 payment."
        }
      }
    }
    arguments 17 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 3ba5e89e93458db0.

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

2 more sit on this domain. All of them.