Vendor Regulatory Evidence
REMOTE · EXPERIMENT-001-PRODUCTION-90C3.UP.RAILWAY.APP · SCANNED SEP 22
Resolve a vendor and buy normalized public OSHA, EPA, and SAM exclusion evidence with provenance.
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 Security83
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 154 tokens (~51/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Vendor Regulatory Evidence MCP server?
Vendor Regulatory Evidence is a hosted endpoint at https://experiment-001-production-90c3.up.railway.app/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 · experiment-001-production-90c3.up.railway.app
claude mcp add --transport http thryvebaseline-agent-services-001 'https://experiment-001-production-90c3.up.railway.app/mcp'
{
"mcpServers": {
"thryvebaseline-agent-services-001": {
"url": "https://experiment-001-production-90c3.up.railway.app/mcp"
}
}
} {
"servers": {
"thryvebaseline-agent-services-001": {
"type": "http",
"url": "https://experiment-001-production-90c3.up.railway.app/mcp"
}
}
} [mcp_servers.thryvebaseline-agent-services-001] url = "https://experiment-001-production-90c3.up.railway.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"thryvebaseline-agent-services-001": {
"type": "remote",
"url": "https://experiment-001-production-90c3.up.railway.app/mcp",
"enabled": true
}
}
} openclaw mcp add thryvebaseline-agent-services-001 --url 'https://experiment-001-production-90c3.up.railway.app/mcp' --transport streamable-http
mcp_servers:
thryvebaseline-agent-services-001:
url: "https://experiment-001-production-90c3.up.railway.app/mcp" {
"McpServers": {
"thryvebaseline-agent-services-001": {
"Transport": "http",
"Url": "https://experiment-001-production-90c3.up.railway.app/mcp"
}
}
} assistant mcp add thryvebaseline-agent-services-001 -t streamable-http -u 'https://experiment-001-production-90c3.up.railway.app/mcp'
{
"mcpServers": {
"thryvebaseline-agent-services-001": {
"type": "http",
"url": "https://experiment-001-production-90c3.up.railway.app/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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 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 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 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 22 Sept 2026 · Probed https://experiment-001-production-90c3.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of experiment-001-production-90c3.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | 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 |
WWW-Authenticate challenge Agent-EVM-V1
Agent-EVM-V1Protected 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://experiment-001-production-90c3.up.railway.app/mcp | Verified | 200 | |
| http (plaintext) | http://experiment-001-production-90c3.up.railway.app/mcp | HTTPS enforced | 301 | https://experiment-001-production-90c3.up.railway.app/mcp |
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 →
build_vendor_evidence_package ~30
Purchase a classified, source-backed vendor regulatory evidence package.
| Name | Type | Req | Description |
|---|---|---|---|
| vendor_token | string | yes | – |
No output schema declared.
No examples provided.
get_vendor_regulatory_records ~37
Purchase normalized OSHA, EPA ECHO, and public SAM exclusion records for a resolved vendor.
| Name | Type | Req | Description |
|---|---|---|---|
| vendor_token | string | yes | – |
No output schema declared.
No examples provided.
resolve_vendor ~87
Resolve a U.S. vendor before payment; ambiguity never creates a charge.
| Name | Type | Req | Description |
|---|---|---|---|
| aliases | array | – | – |
| city | string | – | – |
| company_name | string | yes | – |
| epa_frs_id | string | – | – |
| state | string | yes | – |
| street_address | string | – | – |
| uei | string | – | – |
| zip_code | string | – | – |
No output schema declared.
No examples provided.
What is the Vendor Regulatory Evidence MCP server?
Vendor Regulatory Evidence is an MCP server listed in the public MCP registry as io.github.ThryveBaseline/agent-services-001. Resolve a vendor and buy normalized public OSHA, EPA, and SAM exclusion evidence with provenance. This page covers its hosted endpoint (https://experiment-001-production-90c3.up.railway.app/mcp).
Is the Vendor Regulatory Evidence MCP server safe to use?
Vendor Regulatory Evidence scores 81 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 Vendor Regulatory Evidence MCP server expose?
Vendor Regulatory Evidence exposes 3 tools: resolve_vendor, get_vendor_regulatory_records, build_vendor_evidence_package. Their descriptions and schemas cost roughly 154 tokens of context every time the server is loaded.
Does the Vendor Regulatory Evidence MCP server require authentication?
Yes. Vendor Regulatory Evidence 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 Vendor Regulatory Evidence MCP server still maintained?
Vendor Regulatory Evidence is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.