Official Source Evidence
REMOTE · EVIDENCE.REGULAVITA.COM
Accountless public-source, SEC Form D and OFAC tools with x402 USDC payment on Base.
Available components
Last scanned (38 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 21 Sep 2026.
Category Finance and Payments
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 28 Sept 26 −15
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 26 Sept 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 25 Sept 26 −14
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 22 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.87 → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
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 28 Sept 2026 · Probed https://evidence.regulavita.com/mcp/
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of evidence.regulavita.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| regulavita.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://evidence.regulavita.com/mcp/ | Unreachable | ||
| http (plaintext) | http://evidence.regulavita.com/mcp/ | HTTPS enforced |
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_example_payment ~52
Create a live x402 challenge using this service's known-valid published example for one product. This never moves funds. The returned arguments can be passed unchanged to submit_x402_payment.
| Name | Type | Req | Description |
|---|---|---|---|
| product | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_form_d_funding_leads_payment ~80
Create a live x402 challenge for SEC Form D funding signals. This does not move funds.
| Name | Type | Req | Description |
|---|---|---|---|
| include_amendments | boolean | – | – |
| industry_keywords | – | – | – |
| limit | integer | – | – |
| minimum_amount_sold_usd | string | – | – |
| since | string | yes | – |
| states | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_payment_preflight_payment ~52
Create a live x402 challenge for an exact-address OFAC payment preflight. This does not move funds and is not sanctions clearance.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| network | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_quote ~39
Return a free, side-effect-free quote and exact input example for one paid product. Does not create a payment challenge.
| Name | Type | Req | Description |
|---|---|---|---|
| product | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_service_status ~29
Check live readiness, x402 network and prices before spending. This free call has no side effects.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_source_snapshot_payment ~52
Create a live x402 challenge for one public HTTPS source snapshot. This does not move funds.
| Name | Type | Req | Description |
|---|---|---|---|
| max_characters | integer | – | – |
| query | string | – | – |
| url | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
request_capability ~96
Tell the operator about a machine-service capability you would pay for. The structured request is stored privately for product research; contact_uri is optional and is never called automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_uri | – | – | – |
| current_alternative | string | – | – |
| decision_criteria | – | – | – |
| job_to_be_done | string | yes | – |
| max_budget_usd | – | – | – |
| max_latency_seconds | – | – | – |
| required_output_fields | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
submit_x402_payment ~76
Submit a wallet-generated x402 PAYMENT-SIGNATURE for a previously quoted product. Use exactly the same arguments. Never provide a private key or seed phrase. request_id enables safe result replay.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | object | yes | – |
| payment_signature | string | yes | – |
| product | string | yes | – |
| request_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Official Source Evidence MCP server?
Official Source Evidence is a hosted endpoint at https://evidence.regulavita.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 · evidence.regulavita.com
claude mcp add --transport http joshua-stapleton-official-source-evidence 'https://evidence.regulavita.com/mcp/'
What is the Official Source Evidence MCP server?
Official Source Evidence is an MCP server listed in the public MCP registry as io.github.Joshua-Stapleton/official-source-evidence. Accountless public-source, SEC Form D and OFAC tools with x402 USDC payment on Base. This page covers its hosted endpoint (https://evidence.regulavita.com/mcp/).
Is the Official Source Evidence MCP server safe to use?
Official Source Evidence scores 0 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 Official Source Evidence MCP server expose?
Official Source Evidence exposes 8 tools: get_service_status, get_quote, get_example_payment, request_capability, get_source_snapshot_payment, and 3 more. Their descriptions and schemas cost roughly 476 tokens of context every time the server is loaded.
Does the Official Source Evidence MCP server require authentication?
Its publisher declares no required credentials for Official Source Evidence. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Official Source Evidence MCP server still maintained?
Official Source Evidence has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.