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

verifygrid-api-mcp

https://www.verifygrid.io

Registry code: afd49654207cbb4b

api record

Sub-50ms verification for FMCSA USDOT/MC, CMS NPI, OFAC/OIG/SAM sanctions, and TCPA phone risk.

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

endpoint
https://www.verifygrid.io/mcp also at https://verifygrid.io/mcp
door code
f6d076baac736247
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 it live, free and safe measured by this hub
Is verifygrid-api-mcp live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is verifygrid-api-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does verifygrid-api-mcp have?
10 tools: verify_carrier_fmcsa, screen_sanctions_exclusions, verify_provider_npi, screen_sanctions_ofac_oig, lookup_phone_tcpa_dnc, validate_phone_tcpa, validate_email_signup, lookup_fmcsa_carrier, ….
Is verifygrid-api-mcp 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 100%· all time 100%

latency
154ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
  • unknown → live
_ 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 10 tools
3 open 7 never probed 3 of 10 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.

  • lookup_fmcsa_carrier open 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "mc_number": {
      "type": "string"
    },
    "dot_number": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • lookup_npi_provider open 1h ago

    Alias for verify_provider_npi: Verify healthcare provider NPI registry record, taxonomy specialty, practice location, and HHS OIG LEIE exclusion status.

    mcp-tool

    {
  "type": "object",
  "required": [
    "npi"
  ],
  "properties": {
    "npi": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • check_account_balance open 1h ago

    Return remaining universal credit balance and current subscription tier for the authenticated API/MCP key.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • verify_carrier_fmcsa unknown never probed

    Query live FMCSA USDOT/MC carrier operating authority, BIPD insurance on file, BOC-3 process agent status, and 2027 UCR registration.

    mcp-tool

    {
  "type": "object",
  "required": [
    "dot_number"
  ],
  "properties": {
    "mc_number": {
      "type": "string",
      "description": "Optional MC docket number (e.g. MC-782190)"
    },
    "dot_number": {
      "type": "string",
      "description": "USDOT number (e.g. 2247805 or 4429108)"
    }
  }
}
    arguments 16 lines
  • screen_sanctions_exclusions unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "entity_name"
  ],
  "properties": {
    "country": {
      "type": "string"
    },
    "entity_name": {
      "type": "string"
    }
  }
}
    arguments 14 lines
  • verify_provider_npi unknown never probed

    Verify healthcare provider 10-digit NPI registry record via CMS NPPES, taxonomy specialty, practice location, and HHS OIG LEIE exclusion status.

    mcp-tool

    {
  "type": "object",
  "required": [
    "npi"
  ],
  "properties": {
    "npi": {
      "type": "string",
      "description": "10-digit National Provider Identifier (e.g. 1245319599)"
    }
  }
}
    arguments 12 lines
  • screen_sanctions_ofac_oig unknown never probed

    Screen a company, healthcare entity, or individual against OFAC SDN sanctions, HHS OIG LEIE exclusions, SAM federal debarment, and EPA ECHO enforcement.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "q": {
      "type": "string",
      "description": "Entity or individual name to screen"
    },
    "country": {
      "type": "string",
      "description": "Optional ISO country code (default US)"
    },
    "entity_name": {
      "type": "string",
      "description": "Alias for q (entity or individual name)"
    }
  }
}
    arguments 17 lines
  • lookup_phone_tcpa_dnc unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "phone"
  ],
  "properties": {
    "phone": {
      "type": "string",
      "description": "Phone number in E.164 or national format (e.g. +14155550199)"
    },
    "country_code": {
      "type": "string",
      "default": "US"
    }
  }
}
    arguments 16 lines
  • validate_phone_tcpa unknown never probed

    Alias for lookup_phone_tcpa_dnc: Validate phone number E.164, carrier line type, and TCPA DNC / litigator risk.

    mcp-tool

    {
  "type": "object",
  "required": [
    "phone"
  ],
  "properties": {
    "phone": {
      "type": "string"
    },
    "country_code": {
      "type": "string",
      "default": "US"
    }
  }
}
    arguments 15 lines
  • validate_email_signup unknown never probed

    Check email deliverability, MX/SPF/DMARC records, disposable domain status, and SaaS free-trial abuse risk score.

    mcp-tool

    {
  "type": "object",
  "required": [
    "email"
  ],
  "properties": {
    "email": {
      "type": "string"
    },
    "ip_address": {
      "type": "string"
    }
  }
}
    arguments 14 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 afd49654207cbb4b.

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

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.