VerifyGrid B2B Compliance & Entity Verification MCP server
io.verifygrid/b2b-compliance-verifierverifygrid.iostreamable-httpv1.0.0Scanned
Sub-50ms verification for FMCSA USDOT/MC, CMS NPI, OFAC/OIG/SAM sanctions, and TCPA phone risk.
10 tools: 3 change things and 7 only read.
- Reads private data · 2
- Reads text others write · 0
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
3 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the VerifyGrid B2B Compliance & Entity Verification MCP server can do
The VerifyGrid B2B Compliance & Entity Verification MCP server is published by verifygrid.io, a domain the MCP Registry verified. It has 10 tools. It can create or change data (3 tools: verify_provider_npi, screen_sanctions_ofac_oig and screen_sanctions_exclusions), but cannot delete data. 7 tools only read.
2 tools read private data (verify_carrier_fmcsa and lookup_fmcsa_carrier).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Nov 3, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
10 tools
Changes things 3Claude Code: ask
screen_sanctions_exclusionsAlias for screen_sanctions_ofac_oig: Screen a company or individual against OFAC SDN sanctions, HHS OIG exclusions, SAM federal debarment, and EPA ECHO enforcement.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Alias for screen_sanctions_ofac_oig: Screen a company or individual against OFAC SDN sanctions, HHS OIG exclusions, SAM federal debarment, and EPA ECHO enforcement.
screen_sanctions_ofac_oigScreen a company, healthcare entity, or individual against OFAC SDN sanctions, HHS OIG LEIE exclusions, SAM federal debarment, and EPA ECHO enforcement.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Screen a company, healthcare entity, or individual against OFAC SDN sanctions, HHS OIG LEIE exclusions, SAM federal debarment, and EPA ECHO enforcement.
verify_provider_npiVerify healthcare provider 10-digit NPI registry record via CMS NPPES, taxonomy specialty, practice location, and HHS OIG LEIE exclusion status.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Verify healthcare provider 10-digit NPI registry record via CMS NPPES, taxonomy specialty, practice location, and HHS OIG LEIE exclusion status.
Only reads 7Show 7 read-only tools
check_account_balanceReturn remaining universal credit balance and current subscription tier for the authenticated API/MCP key.No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it Return remaining universal credit balance and current subscription tier for the authenticated API/MCP key.
lookup_fmcsa_carrierAlias for verify_carrier_fmcsa: Query live FMCSA USDOT/MC carrier operating authority, insurance on file, BOC-3 process agent status, and 2027 UCR registration.Reads private dataNo findings
Why it is in this group
- The name "lookup_fmcsa_carrier" says "lookup": a word for reading.
What it can reach
- private-dataThe description's first sentence says "file": it reads files.
Description, as the server wrote it Alias for verify_carrier_fmcsa: Query live FMCSA USDOT/MC carrier operating authority, insurance on file, BOC-3 process agent status, and 2027 UCR registration.
lookup_npi_providerAlias for verify_provider_npi: Verify healthcare provider NPI registry record, taxonomy specialty, practice location, and HHS OIG LEIE exclusion status.No findings
Why it is in this group
- The name "lookup_npi_provider" says "lookup": a word for reading.
Description, as the server wrote it Alias for verify_provider_npi: Verify healthcare provider NPI registry record, taxonomy specialty, practice location, and HHS OIG LEIE exclusion status.
lookup_phone_tcpa_dncValidate phone number E.164 format, NANPA NPA-NXX carrier line type (mobile/landline/voip/toll_free), porting status, and TCPA DNC / serial litigator risk flags.No findings
Why it is in this group
- The name "lookup_phone_tcpa_dnc" says "lookup": a word for reading.
Description, as the server wrote it Validate phone number E.164 format, NANPA NPA-NXX carrier line type (mobile/landline/voip/toll_free), porting status, and TCPA DNC / serial litigator risk flags.
validate_email_signupCheck email deliverability, MX/SPF/DMARC records, disposable domain status, and SaaS free-trial abuse risk score.No findings
Why it is in this group
- The name "validate_email_signup" says "validate": a word for reading.
Description, as the server wrote it Check email deliverability, MX/SPF/DMARC records, disposable domain status, and SaaS free-trial abuse risk score.
validate_phone_tcpaAlias for lookup_phone_tcpa_dnc: Validate phone number E.164, carrier line type, and TCPA DNC / litigator risk.No findings
Why it is in this group
- The name "validate_phone_tcpa" says "validate": a word for reading.
Description, as the server wrote it Alias for lookup_phone_tcpa_dnc: Validate phone number E.164, carrier line type, and TCPA DNC / litigator risk.
verify_carrier_fmcsaQuery live FMCSA USDOT/MC carrier operating authority, BIPD insurance on file, BOC-3 process agent status, and 2027 UCR registration.Reads private dataNo findings
Why it is in this group
- The description's first verb is "query": a word for reading.
What it can reach
- private-dataThe description's first sentence says "query" and "file": it reads files.
Description, as the server wrote it Query live FMCSA USDOT/MC carrier operating authority, BIPD insurance on file, BOC-3 process agent status, and 2027 UCR registration.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 18, 2026, 16:23 UTC, unchanged since Nov 18, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: www.verifygrid.io does not resolve.
Posture changes
- Nov 18, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://www.verifygrid.io/.well-known/oauth-protected-resource to none
- Authorization servers: https://www.verifygrid.io to none
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 4 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://www.verifygrid.io/.well-known/oauth-protected-resource to none
- Authorization servers: https://www.verifygrid.io to none
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http b2b-compliance-verifier https://www.verifygrid.io/mcpclaude mcp add --transport http b2b-compliance-verifier https://www.verifygrid.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__b2b-compliance-verifier__verify_carrier_fmcsa",
"mcp__b2b-compliance-verifier__lookup_phone_tcpa_dnc",
"mcp__b2b-compliance-verifier__validate_phone_tcpa",
"mcp__b2b-compliance-verifier__validate_email_signup",
"mcp__b2b-compliance-verifier__lookup_fmcsa_carrier",
"mcp__b2b-compliance-verifier__lookup_npi_provider",
"mcp__b2b-compliance-verifier__check_account_balance"
],
"ask": [
"mcp__b2b-compliance-verifier__verify_provider_npi",
"mcp__b2b-compliance-verifier__screen_sanctions_ofac_oig",
"mcp__b2b-compliance-verifier__screen_sanctions_exclusions"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as b2b-compliance-verifier. Review it before you use it.
Capability tags behind 2 rules
- mcp__b2b-compliance-verifier__verify_carrier_fmcsa private-data
- mcp__b2b-compliance-verifier__lookup_fmcsa_carrier private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.verifygrid/b2b-compliance-verifier/verify?hash=856190863bc8136956ca3e7fa2c743f4480495e96da65dd1ef812a132202cb2e" | jq -e '.changed == false'Pinned hash 856190863bc8, from Nov 3, 2026, 23:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.verifygrid/b2b-compliance-verifier/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.verifygrid/b2b-compliance-verifier)Source: MCP Registry · repository. Synced Nov 3, 2026, 23:18 UTC.
VerifyGrid B2B Compliance & Entity Verification MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the VerifyGrid B2B Compliance & Entity Verification MCP server safe?
- No scan can promise that. What its definitions show: 10 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the VerifyGrid B2B Compliance & Entity Verification MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the VerifyGrid B2B Compliance & Entity Verification MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the VerifyGrid B2B Compliance & Entity Verification MCP server have?
- 10 tools: 3 write, 7 read. verify_provider_npi, screen_sanctions_ofac_oig, screen_sanctions_exclusions, verify_carrier_fmcsa, lookup_phone_tcpa_dnc, validate_phone_tcpa, validate_email_signup, lookup_fmcsa_carrier and 2 more.
Does the VerifyGrid B2B Compliance & Entity Verification MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the VerifyGrid B2B Compliance & Entity Verification MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the VerifyGrid B2B Compliance & Entity Verification MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 3, 2026.