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

compliance-evidence

https://evidence.dropwatchhq.com

Registry code: 113e76c8fcce9d69

api record

Dated, signed compliance-evidence packs: gov-fact-grounded claims + exclusion screens + trap-facts.

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

endpoint
https://evidence.dropwatchhq.com/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 compliance-evidence live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is compliance-evidence free to use?
Not measured yet.
What tools does compliance-evidence have?
4 tools: verify_pack, build_evidence_pack, ground_claim, screen_entity.
Is compliance-evidence 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
99.7%

90 days 99.2%· all time 99.2%

latency
86ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 597 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • build a signed compliance evidence pack
  • ground a company claim against government facts
  • screen an entity against exclusion lists
  • verify an evidence pack
takes → gives
text → data, documents
tools
4 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

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

  • verify_pack reads unknown never probed

    Verify a previously-issued pack's hash-chain receipt (proves the artifact is unaltered since generatedAt). Pass the pack id.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string"
        }
      }
    }
    arguments 11 lines
  • build_evidence_pack reads unknown never probed

    Build a dated, source-linked, SIGNED compliance-evidence pack for a regulated-AI deployer to file with their auditor. Grounds each ticker's claims against CURRENT public gov facts (contradiction-engine: SEC 10-K vs USAspending), screens each named entity against federal exclusion/sanctions (exclude-feed: OFAC/LEIE/SAM), and runs N trap-fact refusals (planted false facts refuted by live public data). Output is an EVIDENCE ARTIFACT with a hash-chain receipt — NOT a 'you are compliant' claim.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "traps": {
          "type": "array",
          "items": {
            "type": "object"
          },
          "description": "Optional custom trap-fact battery; omit to use the default battery."
        },
        "tickers": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Public-company tickers whose disclosure claims to ground (max 10)."
        },
        "entities": {
          "type": "array",
          "items": {
            "type": "object"
          },
          "description": "Named entities to screen: [{name, npi?, uei?, state?}] (max 20)."
        }
      }
    }
    arguments 26 lines
  • ground_claim reads unknown never probed

    Ground one public-company claim against CURRENT gov facts via the live contradiction-engine. Returns the dual-cited record if a verifiable 10-K-vs-USAspending contradiction exists, else an HONEST null ('checked, no contradiction at medium/high confidence as of T') — itself audit evidence.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ticker"
      ],
      "properties": {
        "ticker": {
          "type": "string"
        }
      }
    }
    arguments 11 lines
  • screen_entity reads unknown never probed

    Screen a named entity across federal exclusion/sanctions lists (OFAC SDN, OFAC Consolidated, OIG LEIE; SAM where enabled) via the live exclude-feed. FCRA-safe KYB/sanctions screen, not a consumer report.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "npi": {
          "type": "string"
        },
        "uei": {
          "type": "string"
        },
        "name": {
          "type": "string"
        },
        "state": {
          "type": "string"
        }
      }
    }
    arguments 20 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 113e76c8fcce9d69.

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

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 dropwatchhq.com 35 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.

27 more sit on this domain. All of them.