com.verisgov.api/data-access
REMOTE · API.VERISGOV.COM · SCANNED SEP 25
Verified federal funding intelligence with sealed provenance; verify any figure at no charge.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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 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
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
claude mcp add --transport http com-verisgov-api-data-access 'https://api.verisgov.com/mcp'
{
"mcpServers": {
"com-verisgov-api-data-access": {
"url": "https://api.verisgov.com/mcp"
}
}
} {
"servers": {
"com-verisgov-api-data-access": {
"type": "http",
"url": "https://api.verisgov.com/mcp"
}
}
} [mcp_servers.com-verisgov-api-data-access] url = "https://api.verisgov.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-verisgov-api-data-access": {
"type": "remote",
"url": "https://api.verisgov.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-verisgov-api-data-access --url 'https://api.verisgov.com/mcp' --transport streamable-http
mcp_servers:
com-verisgov-api-data-access:
url: "https://api.verisgov.com/mcp" {
"McpServers": {
"com-verisgov-api-data-access": {
"Transport": "http",
"Url": "https://api.verisgov.com/mcp"
}
}
} assistant mcp add com-verisgov-api-data-access -t streamable-http -u 'https://api.verisgov.com/mcp'
{
"mcpServers": {
"com-verisgov-api-data-access": {
"type": "http",
"url": "https://api.verisgov.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 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
- 31 Jul 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
- 30 Jul 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
- 27 Jul 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 Jul 26 0
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 25 Sept 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 | 8 Aug 2026 | 6 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 665bfe90f92da7300efb6635520742c8 |
| 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. | present | 19718 | 13 | Verified |
| verisgov.com. | absent | 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 |
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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ref | string | yes | a 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.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | – |
| state | string | yes | state 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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| state | string | yes | – |
| tag | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| before | string | – | YYYY-MM-DD upper bound |
| states | array | – | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| kind | string | – | – |
| query | string | yes | keywords, 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.
| Name | Type | Req | Description |
|---|---|---|---|
| ref | string | yes | artifact ref, e.g. 'rhtp/states/oklahoma' |
| sha3_256 | string | – | optional: your copy's hash to compare |
No output schema declared.
No examples provided.
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 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.