CF Enforcement Check
Registry code: 5e190e8f2860089c
enforcement_check costs $0.05 per call and is paid with x402 on eip155:8453. An unpaid call returns a 402 whose payment-required header carries the payment requirements. enforcement_sources is free and explains the matching method and the limits — read it before acting on a verdict.
- endpoint
- https://enforcement.cfsoft.us/mcp
- door code
- 43a8b3231c4ca33a
- 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 CF Enforcement Check live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
- Is CF Enforcement Check free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does CF Enforcement Check have?
- 2 tools: enforcement_check, enforcement_sources.
- Is CF Enforcement Check 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 98.7%· all time 99%
last good check
of 2 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- check a company for federal enforcement actions
- find regulatory notices and court records for a name
- see how enforcement matching works
- takes → gives
- text → data
- tools
- 2 reads
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 5 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.
through this hub
successful
what callers paid
distinct
last 2026-11-01
concentrated, shared-payto
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
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.
enforcement_check reads unknown 16h ago
Check whether any federal enforcement action, regulatory notice, SEC filing or court record collected by CourtPulse names a company. Costs $0.05 per call via x402. Returns a records_found / no_records verdict, the matching record count, the company names matched on, the agencies involved, the latest date, 90-day and 12-month counts, and whether any match carries a criminal tag. Records about private individuals are not in the dataset. A match means a record NAMES the company — not that it is the subject or that anything was proven.
{ "type": "object", "required": [ "org" ], "properties": { "cik": { "type": "string", "description": "Optional SEC Central Index Key. The only identifier-grade match available." }, "org": { "type": "string", "description": "Organization name, with or without its legal suffix (\"Agridime\", \"Agridime, LLC\")." }, "state": { "type": "string", "description": "Optional two-letter US state code. Narrows to court records in that state." } }, "additionalProperties": false }arguments 21 linesenforcement_sources reads unknown never probed
List what this service reads, how names are matched, what each confidence level and basis means, and what the answers cannot tell you. Free.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 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 id5e190e8f2860089c.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/5e190e8f2860089c/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/5e190e8f2860089c?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.
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.
- exclusions.cfsoft.us CF Exclusion Check
- packages.cfsoft.us CF Package Check