mcpbeat Sign in

Provider Trust — Verify a Source or Provider MCP Server

answering

Provider Trust — Verify a Source or Provider is answering right now. Last checked 2 min ago. It exposes 6 tools.

Verify a source or provider before an AI agent trusts it. Evidence only; unknown stays unknown.

Uptime history 8 days of history · worst day 96%
8 days agonow
98.2%
Uptime 24h
274 of 279 checks
6
Tools
read from the server
1450 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 25

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 4 September 2026. No other catalogue keeps this.

8 Sep a tool changed version
7 Sep a tool changed the parameters it asks for verify_provider
6 Sep 5 tool descriptions were rewritten check_history, check_payment, check_status and 2 more
6 Sep a tool changed the parameters it asks for verify_provider
4 Sep 10 tools disappeared capability_manifest, compare_capabilities, discover_capabilities and 7 more
4 Sep 6 tools appeared check_history, check_identity, check_payment and 3 more
4 Sep a tool changed version

Provider Trust — Verify a Source or Provider does not always answer

Over the last week it answered 98.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add provider-trust --transport http https://www.scriptmasterlabs.com/api/openai-mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "provider-trust": {
      "url": "https://www.scriptmasterlabs.com/api/openai-mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.provider-trust]
url = "https://www.scriptmasterlabs.com/api/openai-mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "provider-trust": {
      "url": "https://www.scriptmasterlabs.com/api/openai-mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "provider-trust": {
      "url": "https://www.scriptmasterlabs.com/api/openai-mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

compare
compare_providers
Compare provider evidence side by side without a fabricated winner or composite score.
history
check_history
Check privacy-safe historical trust evidence.
identity
check_identity
Check live provider identity evidence.
payment
check_payment
Check live x402 contract, readiness, and settlement evidence.
status
check_status
Check the authoritative backend status.
verify
verify_provider
Verify a provider before using it. Live evidence only; unknown stays unknown.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

capability_manifest
removed 4 Sep 2026
compare_capabilities
removed 4 Sep 2026
discover_capabilities
removed 4 Sep 2026
inspect_capability
removed 4 Sep 2026
recommend_capability
removed 4 Sep 2026
system_status
removed 4 Sep 2026
verify_provider_trust
removed 4 Sep 2026
x402_contract
removed 4 Sep 2026
x402_evidence
removed 4 Sep 2026
x402_readiness
removed 4 Sep 2026

Endpoints

URLTransportStateLatencyChecked
https://www.scriptmasterlabs.com/api/openai-mcp streamable-http answering 1535 ms 2 min ago
https://provider-trust-mcp.onrender.com/mcp streamable-http answering 635 ms 3 min ago
https://squeezeos-api.onrender.com/mcp/provider-trust streamable-http answering 708 ms 3 min ago

Alternatives to Provider Trust — Verify a Source or Provider

same job, measured the same way
MUJ428 Trust Layer — VERIFY BEFORE ACT
by wmujahid428-web

MUJ428 verifies intent and evidence before consequential AI-agent actions.

14 tools answering
Vouchtrail
by vouchtrail

Evidence-first trust verdicts for AI-agent services — query one before you transact.

3 tools answering
Pulsefeed X402
by nikolife2016

Verify x402 payment endpoints before an AI agent pays: scam scan, on-chain checks, trust scores.

54 installs/wk 11 tools answering
Voyager Repo
by dir-ai

An AI agent's safe read-only scout to orient in an unknown repository before touching it.

115 installs/wk local only
KnownGate
by knowngate

Food verification for people and AI agents: evidence-backed verdicts, with sources and dates.

4 tools answering
C
TrustNotch
by trustnotch

Tamper-evident audit logs for AI agents: submit, fetch, and verify cryptographic proof bundles.

122 installs/wk local only
Kaval
by usekaval

Verify the facts an agent's action depends on before it acts — ALLOW, REVIEW, or BLOCK.

159 installs/wk local only
Kaval
by lufemc

Verify the facts an agent's action depends on before it acts — ALLOW, REVIEW, or BLOCK.

local only

Provider Trust — Verify a Source or Provider — questions

Answers built from our own checks of this server.

What can Provider Trust — Verify a Source or Provider do?
It exposes 6 tools, read directly from the server on our last check. Among them: check_history, check_identity, check_payment, check_status, compare_providers, verify_provider. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Provider Trust — Verify a Source or Provider working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 274 of 279 checks got a reply (98.2%), average response time 1450 ms. The bar chart above shows every period we have measured.
Did Provider Trust — Verify a Source or Provider ever remove tools?
Yes. capability_manifest, compare_capabilities, discover_capabilities, inspect_capability and 6 more are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
How do I connect Provider Trust — Verify a Source or Provider?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Provider Trust — Verify a Source or Provider need an API key?
No. Provider Trust — Verify a Source or Provider completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Provider Trust — Verify a Source or Provider?
It answers our handshake in 1450 ms on average, which is faster than 2% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.