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

exclude-feed

https://exclude.dropwatchhq.com

Registry code: 754b8d4e4181025a

api record

Screen a business for federal exclusions & sanctions: OFAC SDN, HHS-OIG LEIE, SAM.gov debarment.

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

endpoint
https://exclude.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 exclude-feed live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is exclude-feed free to use?
Not measured yet.
What tools does exclude-feed have?
4 tools: screen_batch, roster_rescreen, watch_entity, screen_exclusion.
Is exclude-feed 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.8%· all time 99.8%

latency
141ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 435 checks · signed record
  • down → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • screen a business for federal exclusions and sanctions
  • bulk screen entities
  • rescreen a vendor roster
  • watch an entity for new exclusions
takes → gives
text → data
tools
3 reads1 changes data
_ 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.

  • screen_batch reads unknown never probed

    Bulk-screen up to 50 entities in one call against all federal exclusion/sanctions lists. Pass an array of names (or {name,npi,state} objects). Returns one verdict per row. Free tool (rate-limited).

    mcp-tool

    {
      "type": "object",
      "required": [
        "entities"
      ],
      "properties": {
        "entities": {
          "type": "array",
          "items": {
            "type": [
              "string",
              "object"
            ]
          },
          "description": "Array of names or {name,npi,uei,state} objects (max 50)."
        }
      }
    }
    arguments 18 lines
  • roster_rescreen reads unknown never probed

    Re-screen an ENTIRE ROSTER of employees, contractors, and vendors against the federal exclusion & sanctions lists (HHS-OIG LEIE, OFAC SDN+Consolidated, SAM.gov debarment) in ONE call, and mint a DATED, ed25519-SIGNED COMPLIANCE RECEIPT. This is the OIG-mandated MONTHLY exclusion check for healthcare billing / RCM / compliance teams: OIG guidance says screen every employee, contractor, and vendor against the LEIE each month, because a single excluded person on a claim triggers Civil Monetary Penalties. The signed receipt is your audit artifact — verifiable offline, proving WHO you screened, against WHICH list build, on WHAT date. Returns per-entity verdicts (cleared vs. flagged) plus a verifiable receipt URL.

    mcp-tool

    {
      "type": "object",
      "required": [
        "roster"
      ],
      "properties": {
        "org": {
          "type": "string",
          "description": "Your organization name (printed on the compliance receipt)."
        },
        "period": {
          "type": "string",
          "description": "Compliance period as YYYY-MM (defaults to the current month)."
        },
        "roster": {
          "type": "array",
          "items": {
            "type": [
              "string",
              "object"
            ]
          },
          "description": "The people/entities to screen. Each is a name string or {name, npi?, uei?, state?} object (max 250)."
        }
      }
    }
    arguments 26 lines
  • watch_entity changes data unknown never probed

    Add an entity to a watchlist that is RE-SCREENED daily. You get alerted (webhook/email) the first time it appears on any federal exclusion or sanctions list. Use for continuous vendor / counterparty monitoring.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "npi": {
          "type": "string"
        },
        "name": {
          "type": "string"
        },
        "email": {
          "type": "string",
          "description": "Optional email alerted on a new hit."
        },
        "webhook": {
          "type": "string",
          "description": "Optional URL POSTed on a new hit."
        }
      }
    }
    arguments 22 lines
  • screen_exclusion reads unknown never probed

    Screen a business entity / vendor / counterparty for FEDERAL EXCLUSIONS & SANCTIONS before you onboard or pay it. One unified, DEDUPED check across OFAC SDN, OFAC Consolidated (sanctions), HHS-OIG LEIE (healthcare exclusions), SAM.gov (federal contractor debarment/suspension), and publicly-available state debarment lists. Returns match / possible-match / no-match, the matched record(s) with source + exclusion type + dates, and a confidence score. FCRA-SAFE: this is KYB/sanctions compliance for entities — NOT a consumer report, not for credit/employment/insurance/tenancy decisions about individuals.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "npi": {
          "type": "string",
          "description": "Optional 10-digit NPI (healthcare) for an exact LEIE match."
        },
        "uei": {
          "type": "string",
          "description": "Optional SAM UEI."
        },
        "name": {
          "type": "string",
          "description": "Legal / business name of the entity to screen."
        },
        "state": {
          "type": "string",
          "description": "Optional 2-letter state to disambiguate name matches."
        },
        "country": {
          "type": "string",
          "description": "Optional country to disambiguate."
        }
      }
    }
    arguments 28 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 754b8d4e4181025a.

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