MCP server for 1Password service accounts — tools and resources for vaults and credentials
Nothing to run from here
Provider Trust — Verify a Source or Provider is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
7
tools declared
remote
at its publisher
—
calls last 7d
What it does
Provider Trust MCP: verify providers before agents trust them + CANON bulk registry lookup (x402).
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http provider-trust-verify-a-source-or-provider-mcp https://provider-trust-mcp.onrender.com/mcp
# 2 — ask your agent for something these tools do
# verify_provider, compare_providers, check_identity and 4 more
Provider Trust — Verify a Source or Provider costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publisher
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http provider-trust-verify-a-source-or-provider-mcp https://provider-trust-mcp.onrender.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
PAID tool ($0.001 USDC via x402, Base). Verify a provider or source before an AI agent trusts or uses it. Returns live evidence only; unknown stays unknown. Send the x402 PAYMENT-SIGNATURE header on the /mcp request; without payment the call returns the canonical x402 challenge (HTTP 402, amount 1000 = $0.001 USDC, payTo of the canonical SML receiver). Settlement is performed by the canonical CANO
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target | string | yes | Public HTTPS provider, source, MCP, A2A, or API URL. |
Compare 2-5 providers using live evidence. No made-up score or winner.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| targets | array | yes | — |
Check live provider identity evidence.
Takes no parameters.
Check live x402 payment readiness and real settlement evidence.
Takes no parameters.
Check recent evidence-backed provider history. Traffic volume is context only and is never presented as buyers, trust, or reputation.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hours | integer | no | — |
Check whether the Provider Trust backend is live.
Takes no parameters.
PAID tool ($0.01 USDC via x402, Base). Resolve up to 100 artifact freshness records in one call against live registries and cryptographically verified CANON publisher manifests: detects stale mirrors, superseded artifacts, and publisher/registry conflicts. Send the x402 PAYMENT-SIGNATURE header on the /mcp request; without payment the call returns the canonical x402 challenge (HTTP 402, amount 100
| Parameter | Type | Required | Notes |
|---|---|---|---|
| items | array | yes | One to 100 package or artifact freshness checks. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Provider Trust — Verify a Source or Provider or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.3.4 · scanned 5 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digesta266b4064a36557f2d4c59d4438997417bb232cb6ec8a1a765a5b11f62f75d80
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| verify_provider | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| compare_providers | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| check_identity | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| check_payment | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| check_history | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| check_status | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| canon_registry_bulk_lookup | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digesta266b4064a36557f
Scanned2026-11-05
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.3.4.
1.3.4
5 Nov 2026
latestNo release note was published with this version.
1.3.3
2 Nov 2026
No release note was published with this version.
1.3.1
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Provider Trust — Verify a Source or Provider can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.