Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.verisgov.api/data-access

REMOTE · API.VERISGOV.COM

Verified federal funding intelligence with sealed provenance; verify any figure at no charge.

Available components

0 this week 75 Trust /100

Last scanned (20 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security77
Transport & Reachability100
Schema Quality & AI Usability29
  • AI-judged instruction clarity (poor).Fail
  • Tool/resource definitions use about 579 tokens (~96/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage85
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 54% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • Manipulation check failed: an AI judge found 1 of 7 captured unit(s) of tool text manipulative, the first being "server instructions". See how to fix → Fail
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 21 Nov 2026 · Probed https://api.verisgov.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=verisgov.com CN=WE1,O=Google Trust Services,C=US 6 Oct 2026 4 Jan 2027 ECDSA 256 ECDSA-SHA256 d3af0c79e252675b13fb6a193d10f63e
SANs: verisgov.com, api.verisgov.com, *.api.verisgov.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.verisgov.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
verisgov.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'none'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer

Protected resource metadata

Retrieved No
Problem No resource metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.verisgov.com/mcp Verified 200
http (plaintext) http://api.verisgov.com/mcp Inconclusive 405
MCP tools · 6 exposed · ~525 tokens

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 →

Tool Tokens
get_document ~86

Primary-document shelf metadata for a state or program ref (title, kind, publication date, source URL, sealed hash where held). tier 'golden' = fidelity-verified; tier 'abstract' = integrity-verified but preliminary, attribute as such.

NameTypeReqDescription
refstringyesa ref from search_programs, e.g. 'rhtp/states/oklahoma'

No output schema declared.

No examples provided.

get_state_profile ~88

A state's RHTP profile: award, lead agency, initiative summaries. response_format 'detailed' adds officials and the primary-document shelf. tier 'golden' = fidelity-verified; tier 'abstract' = integrity-verified but preliminary, attribute as such.

NameTypeReqDescription
response_formatstring––
statestringyesstate slug, e.g. 'oklahoma'

No output schema declared.

No examples provided.

get_subinitiative_ledger ~88

The funded sub-initiative ledger for a state: who is funded, for what, with dollars and RFA timing. tier 'golden' = fidelity-verified; tier 'abstract' = integrity-verified but preliminary, attribute as such.

NameTypeReqDescription
cursorstring––
statestringyes–
tagstring–filter by keyword in name/description

No output schema declared.

No examples provided.

list_live_deadlines ~69

Open/closing solicitations and key dates across your entitled states and programs. tier 'golden' = fidelity-verified; tier 'abstract' = integrity-verified but preliminary, attribute as such.

NameTypeReqDescription
beforestring–YYYY-MM-DD upper bound
statesarray––

No output schema declared.

No examples provided.

search_programs ~98

Search the verified federal-funding corpus (states, initiatives, sub-initiatives, programs) by keywords. Returns ranked stubs with refs for follow-up tools. tier 'golden' = fidelity-verified; tier 'abstract' = integrity-verified but preliminary, attribute as such.

NameTypeReqDescription
cursorstring––
kindstring––
querystringyeskeywords, e.g. 'maternal remote monitoring'

No output schema declared.

No examples provided.

verify_seal ~96

Cryptographically verify an artifact: recomputes its SHA3-256, checks the signed manifest entry and the Ed25519 manifest signature. Pass sha3_256 to attest a copy you hold. Verification is free of charge.

NameTypeReqDescription
refstringyesartifact ref, e.g. 'rhtp/states/oklahoma'
sha3_256string–optional: your copy's hash to compare

No output schema declared.

No examples provided.

Install

How do I install the com.verisgov.api/data-access MCP server?

com.verisgov.api/data-access is a hosted endpoint at https://api.verisgov.com/mcp, 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 · api.verisgov.com

# add to Claude Code
claude mcp add --transport http com-verisgov-api-data-access 'https://api.verisgov.com/mcp'
Common questions

What is the com.verisgov.api/data-access MCP server?

com.verisgov.api/data-access is an MCP server listed in the public MCP registry as com.verisgov.api/data-access. Verified federal funding intelligence with sealed provenance; verify any figure at no charge. This page covers its hosted endpoint (https://api.verisgov.com/mcp).

Is the com.verisgov.api/data-access MCP server safe to use?

com.verisgov.api/data-access scores 75 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 com.verisgov.api/data-access MCP server expose?

com.verisgov.api/data-access exposes 6 tools: search_programs, get_state_profile, get_subinitiative_ledger, list_live_deadlines, get_document, verify_seal. Their descriptions and schemas cost roughly 525 tokens of context every time the server is loaded.

Does the com.verisgov.api/data-access MCP server require authentication?

Yes. com.verisgov.api/data-access asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the com.verisgov.api/data-access MCP server still maintained?

com.verisgov.api/data-access is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the com.verisgov.api/data-access MCP server?

VerifyMCP ran 12 checks on com.verisgov.api/data-access, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about com.verisgov.api/data-access: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.