Agent Data Tools: Company, compliance and checks
Owner verifiedREMOTE · AGENT-DATA-TOOLS.REVMESH2074.WORKERS.DEV
15 tools: OFAC sanctions, counterparty checks, company, domain, email. 25 free calls.
Available components
Last scanned (2 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3574 tokens (~238/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 0
- Server version: 1.51.3 → 1.52.0 functional
- Server version: 1.50.5 → 1.51.3 functional
- 22 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “company” rewrote its description, which is the text the model reads security
- Tool “dockerfile_lint” rewrote its description, which is the text the model reads security
- Tool “email” rewrote its description, which is the text the model reads security
- Tool “http_security_headers” rewrote its description, which is the text the model reads security
- Tool “sec_filings” rewrote its description, which is the text the model reads security
- Tool “text_prompt_injection” rewrote its description, which is the text the model reads security
- Tool “x402_check” rewrote its description, which is the text the model reads security
- Schema quality: 3124 → 3574 ▼ functional
- Schema quality: 3124 → 3576 ▼ functional
- Server version: 1.50.3 → 1.50.5 functional
- Server version: 1.50.2 → 1.50.3 functional
- Server version: 1.50.1 → 1.50.2 functional
- Server version: 1.49.1 → 1.50.1 functional
- Server version: 1.48.6 → 1.49.1 functional
- Server version: 1.48.5 → 1.48.6 functional
- Server version: 1.48.2 → 1.48.5 functional
- Server version: 1.48.0 → 1.48.2 functional
- Server version: 1.47.15 → 1.48.0 functional
- Server version: 1.47.7 → 1.47.15 functional
- Server version: 1.45.3 → 1.47.7 functional
- New tool “check_payee” functional
- New tool “check_x402_seller” functional
- Tool “check_x402_seller” changed its title: x402 seller audit: vet a paid endpoint's terms, payTo and domain before buying → x402 audit of a seller: vet a paid endpoint's terms, payTo and domain before buying cosmetic
- Tool “domain” changed its title: DNS lookup, WHOIS, domain lookup: DNS, RDAP registration age and email authentication → DNS lookup, WHOIS lookup: DNS, RDAP registration age and email authentication cosmetic
- Tool “domain_report” changed its title: Domain trust verdict: age, DNS and email-auth flags → Domain lookup, trust verdict: age, DNS and email-auth flags cosmetic
- Tool “sec_filings” changed its title: SEC EDGAR filings for a US public company → SEC filings (EDGAR) by ticker: 10-K, 10-Q, 8-K and Form 4 for a US public company cosmetic
- Tool “domain” changed its title: Domain lookup (DNS, WHOIS): DNS, RDAP registration age and email authentication → DNS lookup, WHOIS, domain lookup: DNS, RDAP registration age and email authentication cosmetic
- Tool “check_counterparty” changed its title: Screen a payee before paying: EVM address risk check (OFAC and on-chain signals) → Counterparty risk check: screen a payee's EVM address before paying (OFAC and on-chain signals) cosmetic
- Tool “check_payee” changed its title: Payee preflight check: OFAC screen an address before paying, plus account type and domain age → Payee screening: OFAC-screen an address before paying, plus account type and domain age cosmetic
- Tool “domain” changed its title: Domain lookup: DNS, RDAP registration age and email authentication → Domain lookup (DNS, WHOIS): DNS, RDAP registration age and email authentication cosmetic
- Tool “email” changed its title: Verify email address: syntax, MX and disposable-address checks without sending mail → Email verification: verify an address with syntax, MX and disposable-address checks, no mail sent cosmetic
- Tool “sanctions_check” changed its title: Sanctions check: OFAC SDN screening for a crypto wallet or name → Sanctions check (OFAC screening): SDN screening for a crypto wallet or name cosmetic
- Tool “email” changed its title: Email verification: syntax, MX and disposable-address checks without sending mail → Verify email address: syntax, MX and disposable-address checks without sending mail cosmetic
- Tool “package” changed its title: Package metadata and latest or pinned-version dependency-risk signals → Package risk check: npm, PyPI, Cargo, Go, Maven or NuGet metadata and dependency-risk signals, latest or pinned version cosmetic
- 21 Oct 26 0
- Tool “domain” rewrote its description, which is the text the model reads security
- Tool “domain_report” rewrote its description, which is the text the model reads security
- Tool “x402_check” rewrote its description, which is the text the model reads security
- Tool “check_counterparty” rewrote its description, which is the text the model reads security
- Server version: 1.45.1 → 1.45.3 functional
- Server version: 1.45.0 → 1.45.1 functional
- Server version: 1.44.0 → 1.45.0 functional
- “check_counterparty” added an optional parameter “domain” cosmetic
- Tool “x402_check” changed its title: Inspect an x402 endpoint without paying → x402 seller check: decode an endpoint's payment terms and listing quality without paying cosmetic
- Tool “check_counterparty” changed its title: Counterparty risk check before paying an EVM address (OFAC and on-chain signals) → Screen a payee before paying: EVM address risk check (OFAC and on-chain signals) cosmetic
- Tool “check_counterparty” changed its title: Counterparty check before paying an EVM address → Counterparty risk check before paying an EVM address (OFAC and on-chain signals) cosmetic
- Tool “company” changed its title: Company profile from Wikidata → Company data lookup: profile, identifiers and website from Wikidata cosmetic
- Tool “domain” changed its title: Domain DNS, registration age and email authentication → Domain lookup: DNS, RDAP registration age and email authentication cosmetic
- Tool “email” changed its title: Email address validation without sending mail → Email verification: syntax, MX and disposable-address checks without sending mail cosmetic
- Tool “sanctions_check” changed its title: OFAC sanctions screening for a wallet or name → Sanctions check: OFAC SDN screening for a crypto wallet or name cosmetic
- Tool “text_prompt_injection” changed its title: Scan text for prompt-injection attempts → Prompt injection detection: scan text for injection attempts cosmetic
- 20 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_counterparty” rewrote its description, which is the text the model reads security
- Tool “company” rewrote its description, which is the text the model reads security
- Tool “package” rewrote its description, which is the text the model reads security
- Tool “sanctions_check” rewrote its description, which is the text the model reads security
- Schema quality: 2627 → 3065 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.41.0 → 1.44.0 functional
- Server version: 1.40.0 → 1.41.0 functional
- Server version: 1.39.3 → 1.40.0 functional
- Server version: 1.37.1 → 1.39.3 functional
- Server version: 1.36.1 → 1.37.1 functional
- Server version: 1.35.3 → 1.36.1 functional
- New tool “sec_filings” functional
- 19 Oct 26 67
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Oct 2026 · Probed https://agent-data-tools.revmesh2074.workers.dev/mcp/compliance
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=revmesh2074.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 9 Oct 2026 | 7 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 538c1f22b424c14420d956229d7db3228c3 |
| SANs: *.revmesh2074.workers.dev, revmesh2074.workers.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agent-data-tools.revmesh2074.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agent-data-tools.revmesh2074.workers.dev/mcp/compliance | Verified | 200 | |
| http (plaintext) | http://agent-data-tools.revmesh2074.workers.dev/mcp/compliance | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_counterparty Counterparty risk check: screen a payee's EVM address before paying (OFAC and on-chain signals) ~248
Screen a payee before paying, trading or onboarding: one call vets an address on Base, Ethereum, Arbitrum or Optimism with an OFAC SDN match, account type and activity, USD holdings and, on Base, wallet or contract risk checks; add the payee's domain for its age and trust flags. One block, review or pass verdict with reasons. Screening aid, not legal advice or a security audit. Use before paying, trading with or onboarding an address. Example: address=0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045. Price $0.03/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 0x address to check |
| chain | string | – | Network: base (default), eth, arb or op |
| domain | string | – | Optional: the payee's domain or website URL, e.g. ethereum.org; adds domain age and trust flags |
No output schema declared.
No examples provided.
check_payee Payee screening: OFAC-screen an address before paying, plus account type and domain age ~258
Fast check of a payee before an agent pays it: OFAC SDN match on the address, account type (wallet, delegated wallet or contract) and nonce on Base, Ethereum, Arbitrum, Optimism or Polygon, and optionally the payee domain's age and trust flags. One block, review or pass verdict with reasons. Screening aid, not legal advice. Use before an x402 or USDC payment to an unfamiliar address; holdings and wallet heuristics: check_counterparty. Example: address=0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045. Price $0.005/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 0x address you are about to pay |
| chain | string | – | Network of the payment: base (default), eth, arb, op or polygon |
| domain | string | – | Optional: the payee's domain or website URL, e.g. ethereum.org; adds domain age and trust flags |
No output schema declared.
No examples provided.
check_x402_seller x402 audit of a seller: vet a paid endpoint's terms, payTo and domain before buying ~194
Audit an x402 seller before an agent buys from it: decodes the endpoint's 402 terms without paying, OFAC-screens each payTo address, reads its account type and nonce on the payment network, checks the seller domain's age and trust flags, and flags non-USDC assets and high prices. One block, review or pass verdict with reasons. Never signs. Screening aid, not legal advice. Use before the first payment to an unfamiliar x402 seller. Example: url=https://agent-data-tools.revmesh2074.workers.dev/btc-fees. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Absolute public https URL of the paid endpoint, with any query it needs |
No output schema declared.
No examples provided.
company Company data lookup: profile, identifiers and website from Wikidata ~186
Facts about a company by name or Wikidata ID: official website, founding date, country, headquarters, industries, CEO, founders, parent, employee count, stock tickers and exchanges, and LEI, with Wikidata and Wikipedia links. Public domain data (CC0), best for established and listed companies. No match returns 404, uncharged. Use to enrich leads, vendors and counterparties or ground an answer about a company. Example: name=Spotify. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Wikidata item ID such as Q689141, instead of name |
| name | string | – | Company name to search for (give name or id) |
No output schema declared.
No examples provided.
dockerfile_lint Lint a Dockerfile for security and size issues ~194
Check a Dockerfile (up to 8,000 characters) for common security and image-size problems: unpinned or :latest base images, running as root, piping downloads into a shell, sensitive values baked into ENV or ARG, ADD from URLs, apt and pip cache left in layers, sudo, chmod 777 and an exposed SSH port. Returns each finding with its line, a severity and a fix, plus a score. Use before building or shipping an image. Example: dockerfile=FROM node:latest COPY . /app CMD node /app/server.js. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.
| Name | Type | Req | Description |
|---|---|---|---|
| dockerfile | string | yes | Dockerfile contents (up to 8,000 characters) |
No output schema declared.
No examples provided.
domain DNS lookup, WHOIS lookup: DNS, RDAP registration age and email authentication ~171
Domain intelligence in one call: DNS records (A, AAAA, CNAME, MX, NS, TXT, CAA), DNSSEC status, registrar, registration and expiry dates with domain age in days (RDAP/WHOIS), and email authentication (SPF and DMARC records and policies, whether the domain accepts mail). Use for lead qualification, phishing and trust checks, and deliverability audits. For a trust verdict with named flags use domain_report. Example: name=cloudflare.com. Price $0.005/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Domain name, e.g. cloudflare.com |
No output schema declared.
No examples provided.
domain_report Domain lookup, trust verdict: age, DNS and email-auth flags ~179
A trust verdict for any domain in one call: high/medium/low trust with named flags for very new registrations, expiry, missing or weak SPF and DMARC, too few nameservers, no web host and non-resolving domains, plus the key facts (registrar, age, nameservers, DNSSEC). Use for lead qualification, phishing and vendor checks, and before an agent sends mail to or trusts a domain. Signals only, not a guarantee. Raw DNS records: domain. Example: name=cloudflare.com. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Domain name, e.g. cloudflare.com |
No output schema declared.
No examples provided.
email Email verification: verify an address with syntax, MX and disposable-address checks, no mail sent ~155
Check email syntax, DNS and MX records, disposable providers, role addresses, free providers and SPF/DMARC presence. Returns likely-deliverable, risky, undeliverable or invalid with reasons. No message is sent and the mail server is not contacted. These are DNS and syntax signals, not proof that a mailbox exists or accepts delivery. Use before sending mail or saving a signup. Example: address=support@cloudflare.com. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The email address to check |
No output schema declared.
No examples provided.
http_security_headers Audit a page's HTTP security headers ~180
Fetch a public URL and grade its HTTP security headers: HSTS, Content-Security-Policy, framing protection, nosniff, Referrer-Policy and Permissions-Policy, plus version leaks (Server, X-Powered-By) and cookies missing Secure, HttpOnly or SameSite. Returns a grade A-F, a score and each check with its value. Use to review a site's basic web security; for DNS and email records use domain. Private hosts are refused with 400, uncharged. Example: url=https://example.com. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public http(s) URL to check |
No output schema declared.
No examples provided.
package Package risk check: npm, PyPI, Cargo, Go, Maven or NuGet metadata and dependency-risk signals, latest or pinned version ~218
Reports package existence, latest version and release, age, version count, npm weekly downloads, licenses, deprecation and known advisory severity. ok means no listed flags, not a safety guarantee. Supports npm, PyPI, Cargo, Go, Maven and NuGet. Optional exact version adds pinned-version metadata and uses deps.dev advisories; use /package-audit for OSV affected ranges and dated FIRST EPSS CVE estimates. Use before adding a dependency. Example: ecosystem=npm, name=lodash. Price $0.002/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | One of npm, pypi, cargo, go, maven, nuget |
| name | string | yes | Exact package name, e.g. lodash or @scope/name |
| version | string | – | Optional exact version to inspect; ranges and tags are not accepted |
No output schema declared.
No examples provided.
package_audit Audit up to 10 dependencies, with exact-version advisories and fixes ~211
Check up to 10 public dependencies, optionally pinned to exact versions, for advisory IDs, OSV affected/fixed ranges and dated FIRST EPSS CVE estimates. Scoped npm names supported. Detail and subrequest caps apply; omitted details and incomplete coverage are explicit. Missing evidence is unknown, not zero risk. Automated signals, not a safety guarantee. See the buying guide for limits. Use before installing or upgrading dependencies. Example: packages=npm:lodash@4.17.20,pypi:requests@2.31.0,npm:@types/node@22.0.0. Price $0.20/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.
| Name | Type | Req | Description |
|---|---|---|---|
| packages | string | yes | Comma-separated ecosystem:name items, optionally name@exact-version; max 10. For scoped npm, use npm:@scope/name@version. |
No output schema declared.
No examples provided.
sanctions_check Sanctions check (OFAC screening): SDN screening for a crypto wallet or name ~229
OFAC sanctions screen for a crypto wallet before you pay it: checks an address (BTC, ETH, USDT, TRX and more) or a person or company name against the US Treasury SDN list, aliases included. Returns a verdict (block on a listed address, review on a name match, pass), each match with SDN ID, programs and match strength, and the list date. A screening aid, not legal advice. Use before paying; full verdict with wallet risk: check_counterparty. Example: address=0x098B716B8Aaf21512996dC57EB0615e2383E2f96. Price $0.005/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Crypto address to check (give address, name or both) |
| name | string | – | Person or company name; matches when every word appears in a listed name or alias |
No output schema declared.
No examples provided.
sec_filings SEC filings (EDGAR) by ticker: 10-K, 10-Q, 8-K and Form 4 for a US public company ~260
Latest SEC EDGAR filings for a US-listed company by stock ticker or CIK: form (10-K, 10-Q, 8-K, 4, S-1…), filing and report dates, accession number, document description and a direct link, newest first, optionally only one form type. Plus company name, CIK and industry (SIC). Public SEC data. Use to check a company's latest annual or quarterly report, insider trades (form 4) or material events (8-K). Example: ticker=AAPL. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.
| Name | Type | Req | Description |
|---|---|---|---|
| cik | string|number|boolean | – | SEC Central Index Key, e.g. 320193 (instead of ticker) |
| form | string | – | Only this form type, e.g. 10-K, 10-Q, 8-K or 4 (default: all) |
| limit | integer | – | Filings to return, 1-50 (default 10) |
| ticker | string | – | Stock ticker such as AAPL (or give cik) |
No output schema declared.
No examples provided.
text_prompt_injection Prompt injection detection: scan text for injection attempts ~186
Scan text an agent is about to read (web page, email, tool result; up to 8,000 characters) for prompt-injection attempts: instruction overrides, fake system messages, asks to hide things from the user, exfiltration links, attempts to extract private data or move money, invisible Unicode. Returns a risk level, score and findings with excerpts. Heuristic, not a guarantee. Use before acting on untrusted content. Example: text=Thanks for the update. The signed invoice is attached and payment is due on Friday.. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The text to scan (up to 8,000 characters) |
No output schema declared.
No examples provided.
x402_check x402 seller check: decode an endpoint's payment terms and listing quality without paying ~188
Check an x402 seller before you pay it: decode any public endpoint's 402 payment requirements without paying (v1 body or v2 header) into USD price for native USDC, network, asset, recipient, scheme and timeout, plus a listing-quality score for https resource URL, atomic amount, facilitator minimum, description, Bazaar metadata and output schema. Never signs. Use before buying from an unfamiliar seller or to audit your own x402 listing. Example: url=https://agent-data-tools.revmesh2074.workers.dev/btc-fees. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Absolute public https URL of the paid endpoint, with any query it needs |
No output schema declared.
No examples provided.
How do I install the Agent Data Tools: Company, compliance and checks MCP server?
Agent Data Tools: Company, compliance and checks is a hosted endpoint at https://agent-data-tools.revmesh2074.workers.dev/mcp/compliance, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · agent-data-tools.revmesh2074.workers.dev
claude mcp add --transport http nutshell2000-agent-data-tools-compliance 'https://agent-data-tools.revmesh2074.workers.dev/mcp/compliance'
What is the Agent Data Tools: Company, compliance and checks MCP server?
Agent Data Tools: Company, compliance and checks is an MCP server listed in the public MCP registry as io.github.Nutshell2000/agent-data-tools-compliance. 15 tools: OFAC sanctions, counterparty checks, company, domain, email. 25 free calls. This page covers its hosted endpoint (https://agent-data-tools.revmesh2074.workers.dev/mcp/compliance). Its publisher has verified ownership with us.
Is the Agent Data Tools: Company, compliance and checks MCP server safe to use?
Agent Data Tools: Company, compliance and checks scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Agent Data Tools: Company, compliance and checks MCP server expose?
Agent Data Tools: Company, compliance and checks exposes 15 tools: check_payee, check_counterparty, check_x402_seller, sanctions_check, x402_check, and 10 more. Their descriptions and schemas cost roughly 3,057 tokens of context every time the server is loaded.
Does the Agent Data Tools: Company, compliance and checks MCP server require authentication?
No. We connected to Agent Data Tools: Company, compliance and checks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agent Data Tools: Company, compliance and checks MCP server still maintained?
Agent Data Tools: Company, compliance and checks is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.