← Back to search
Search • Rankings • TrustOps • Docs • Pricing • Claim/Manage
awesome-shieldzcash/shieldz-mcp

ShieldZCash/shieldz-mcp

ShieldZCash/shieldz-mcp ShieldZCash/shieldz-mcp](https://glama.ai/mcp/servers/ShieldZCash/shieldz-mcp) 📇 ☁️ 🏠 - Keyless, non-custodial crypto payments. Create crypto payment links and tip jars with just a wallet address, no API key, no signup. Funds settle directly to the merchant’s wallet. Remote at https://shieldz.cash/mcp or `npx @shieldz/mcp`.

JSON report • Policy • Badge metadata • History API •
• Global feed
DECISION SUMMARY

Block For Production

Score
54.7
Rank suppressed while production readiness shows a blocking verdict.
Confidence
High
Based on evidence completeness, recency, and validation density.
Evidence age
9.3h old
Freshness: fresh. Snapshot trustsnap_5818b3d2103e8cc1.
Top risk drivers
  • Utility Coverage
  • Transport Compliance
  • Step Up Auth
Recommended actions
  • Add an explicit confirm/dry-run parameter or two-step confirmation flow to write, delete, exec, and egress-capable tool…
  • Align MCP-Protocol-Version, MCP-Session-Id, DELETE teardown, and expired-session handling with the transport spec.
  • Serve /.well-known/oauth-protected-resource and point it at your authorization server metadata.
Next action
revalidate, add safeguards, export policy
exec-capable tools + no confirmation safeguards + high-risk tools need review + score below evaluation threshold
Compare alternatives Export policy Open report JSON Dispute this assessment
Observed Attention
No observed attention
No observed attention in the current 30-day window.
  • No segmented attention signals observed in the current window.
Bucketed signal based on recent segmented Verify telemetry. Crawler and evaluator activity is not treated as confirmed human demand.
Risks Compatibility Evidence Fix it Governance History Technical details
Status
Healthy
Score
54.7
Transport
streamable-http
Tools
3
Ownership
Unclaimed
Claim, revalidate, or manage this server
DISPUTE THIS ASSESSMENT

Dispute this assessment

If any published claim about this server -- its score, a risk flag, a capability classification, or its taxonomy -- is factually wrong, tell us what evidence shows and we will review it. This does not require claiming or verifying ownership of the server first.

Verify responds to disputes within 5 business days and resolves them within 15.

Dispute history

No disputes filed for this server.

Risks

Security posture
Tools analyzed
3
High-risk tools
2
Destructive tools
0
Exec tools
1
Egress tools
0
Secret tools
1
Bulk-access tools
0
Risk distribution
medium:1, high:1, critical:1
Tool capability & risk inventory
ToolCapabilitiesRiskFindingsNotesEvidence
create_tip_jar write exec financial Critical command execution financial transaction No explicit safeguard hints detected.
Schema & evidence 
{
  "annotations": {},
  "capabilities": [
    "write",
    "exec",
    "financial"
  ],
  "input_schema": {
    "properties": {
      "address": {
        "description": "Destination wallet (0x EVM address); funds settle here.",
        "type": "string"
      },
      "asset": {
        "description": "Stablecoin (default USDC)",
        "enum": [
          "USDC",
          "USDT"
        ],
        "type": "string"
      },
      "chain": {
        "description": "Settlement chain (default base)",
        "enum": [
          "base",
          "arbitrum",
          "optimism",
          "polygon",
          "ethereum"
        ],
        "type": "string"
      },
      "description": {
        "type": "string"
      },
      "email": {
        "description": "Optional, lets the owner claim a dashboard later",
        "type": "string"
      },
      "slug": {
        "description": "Optional custom URL slug",
        "type": "string"
      },
      "suggested_amounts_usd": {
        "description": "Preset amount buttons in USD, e.g. [3, 5, 10]",
        "items": {
          "type": "number"
        },
        "type": "array"
      },
      "title": {
        "description": "Heading shown on the tip page, e.g. 'Buy me a coffee'",
        "type": "string"
      }
    },
    "required": [
      "address"
    ],
    "type": "object"
  },
  "risk_flags": [
    "command_execution",
    "financial_transaction"
  ]
}
Dispute this classification
get_account_status read write secrets Medium secret material access No explicit safeguard hints detected.
Schema & evidence 
{
  "annotations": {},
  "capabilities": [
    "read",
    "write",
    "secrets"
  ],
  "input_schema": {
    "properties": {
      "manage_token": {
        "description": "The manage_token from create_payment_link / create_tip_jar",
        "type": "string"
      }
    },
    "required": [
      "manage_token"
    ],
    "type": "object"
  },
  "risk_flags": [
    "secret_material_access"
  ]
}
Dispute this classification
Write-action governance
Governance status
Error
Safe to publish
✕
Auth boundary
public_or_unclear
Blast radius
Medium
High-risk tools
2
Confirmation signals
create_tip_jar
Safeguard count
0

Status detail: 2 high-risk tool(s), 1 exec-capable tool(s) are exposed without a clear auth boundary; 0 safeguard(s) and 1 confirmation signal(s) detected.

ToolRiskFlagsSafeguards
create_payment_link High financial transaction no
create_tip_jar Critical command execution financial transaction no
Action-controls diff
Snapshot changed
no
Disabled-by-default candidates
none
New actions
ActionRiskFlags
No newly added actions.
Changed actions
ActionChange typesRisk
No materially changed actions.
Critical alerts
High/critical-severity alerts
6
Production verdicts degrade quickly when high or critical-severity alerts are active.

Compatibility

Client compatibility verdicts

Client compatibility only means the server shape can work with a client. Production trust decision and write-action publishing are evaluated separately so a client-compatible server can still be blocked for production.

Client compatibility: ChatGPT
Not client-compatible
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Transport compliance failed or did not complete successfully.; OAuth interoperability should be strong.; The tool surface is not limited to search/fetch-style read tools.; This client profile expects a read/search-only tool surface, but write, delete, or exec-capable tools are present.
Confidence: high (75.5)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initialize • OK
  • tools_list • OK
  • transport_compliance_probe • Error
  • step_up_auth_probe • Missing
  • connector_replay_probe • OK — Frozen tool snapshots must survive refresh.
  • request_association_probe • Missing — Roots, sampling, and elicitation should stay request-scoped.
Client compatibility: Claude
Not client-compatible
Transport behavior should match Claude-compatible HTTP expectations.; The tool surface is not limited to search/fetch-style read tools.; This client profile expects a read/search-only tool surface, but write, delete, or exec-capable tools are present.; OAuth is not configured, so this client cannot authenticate without additional setup.; Not yet safe for company-knowledge use: requires a search/fetch-only surface with no export, bulk, mutating, or high-blast-radius exposure.; Not yet safe for the Messages API remote MCP path: requires OAuth, a compatible connector profile, and no pending connector-refresh risk.
Confidence: high (75.5)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initialize • OK
  • tools_list • OK
  • transport_compliance_probe • Error
Write-action publishing
Publishing blocked
action_safety_probe reported an unconfirmed high-risk, destructive, or exec-capable tool. Risky write actions are present without a clear auth boundary and confirmation signal.
Confidence: high (75.5)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history
Disagreements: none
  • action_safety_probe • Error
Snapshot churn risk
Low
No material tool-surface churn detected in the latest comparison.
Confidence: high (75.5)
Evidence provenance
Winner: history
Supporting sources: history, live_validation
Disagreements: none
  • tool_snapshot_probe • OK
  • connector_replay_probe • OK
Client compatibility gate details
ChatGPT custom connector
Not client-compatible
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Transport compliance failed or did not complete successfully.; OAuth interoperability should be strong.; The tool surface is not limited to search/fetch-style read tools.; This client profile expects a read/search-only tool surface, but write, delete, or exec-capable tools are present.
Remediation checklist
  • Add OAuth-based authentication for remote connector auth.
  • Support dynamic client registration (DCR) to simplify connector setup.
  • Resolve the transport compliance failure -- see the transport compliance probe evidence for what specifically broke.
  • Improve OAuth interoperability -- see the OAuth Interop score breakdown.
  • Limit the exposed surface to search/fetch-style read tools.
  • Remove or isolate write, delete, and exec-capable tools before using this read/search-only client profile.
Claude remote MCP
Not client-compatible
Transport behavior should match Claude-compatible HTTP expectations.; The tool surface is not limited to search/fetch-style read tools.; This client profile expects a read/search-only tool surface, but write, delete, or exec-capable tools are present.; OAuth is not configured, so this client cannot authenticate without additional setup.; Not yet safe for company-knowledge use: requires a search/fetch-only surface with no export, bulk, mutating, or high-blast-radius exposure.; Not yet safe for the Messages API remote MCP path: requires OAuth, a compatible connector profile, and no pending connector-refresh risk.
Remediation checklist
  • Resolve the transport compliance failure -- see the transport compliance probe evidence for what specifically broke.
  • Limit the exposed surface to search/fetch-style read tools.
  • Remove or isolate write, delete, and exec-capable tools before using this read/search-only client profile.
  • Configure OAuth for authenticated remote MCP access.
  • Remove export, bulk, mutating, and high-blast-radius exposure before certifying company-knowledge use.
  • Satisfy OAuth, compatibility, and connector-refresh requirements before using the Messages API remote MCP path.
Write-safe publishing
Blocked
Risky write or non-read tools are exposed without a clear auth boundary.; Exec-capable tools are exposed.; Production readiness shows a blocking verdict.
Remediation checklist
  • Add a clearer auth boundary around risky write actions.
  • Constrain or sandbox exec-capable tools before publishing broadly.
  • Resolve the blocking production-readiness verdict before treating this as write-safe.
Verdict traces
Production verdict
Needs remediation
Current validation evidence shows operational or discovery gaps that should be fixed first.
Confidence: high (75.5)
Winning source: live_validation
Triggering alerts
  • No active alert triggers.
Client verdict trace table
VerdictStatusChecksWinning sourceConflicts
openai_connectors Not client-compatible initialize, tools_list, transport_compliance_probe, step_up_auth_probe, connector_replay_probe, request_association_probe live_validation none
claude_desktop Not client-compatible initialize, tools_list, transport_compliance_probe live_validation none
unsafe_for_write_actions Publishing blocked action_safety_probe live_validation none
snapshot_churn_risk Low tool_snapshot_probe, connector_replay_probe history none
Publishability policy profiles
ChatGPT custom connector compatibility
Compatible with review
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Transport compliance failed or did not complete successfully.; OAuth interoperability should be strong.; The tool surface is not limited to search/fetch-style read tools.; This client profile expects a read/search-only tool surface, but write, delete, or exec-capable tools are present. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.
  • Search Fetch Only: No
  • Write Actions Present: Yes
  • Oauth Configured: No
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No
Claude remote MCP compatibility
Connector-compatible
Transport behavior should match Claude-compatible HTTP expectations.; The tool surface is not limited to search/fetch-style read tools.; This client profile expects a read/search-only tool surface, but write, delete, or exec-capable tools are present.; OAuth is not configured, so this client cannot authenticate without additional setup.; Not yet safe for company-knowledge use: requires a search/fetch-only surface with no export, bulk, mutating, or high-blast-radius exposure.; Not yet safe for the Messages API remote MCP path: requires OAuth, a compatible connector profile, and no pending connector-refresh risk. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.
  • Search Fetch Only: No
  • Write Actions Present: Yes
  • Oauth Configured: No
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No
Compatibility fixtures
ChatGPT custom connector fixture
Degraded
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Transport compliance failed or did not complete successfully.; OAuth interoperability should be strong.
  • remote_http_endpoint: Passes
  • oauth_discovery: Degraded
  • frozen_tool_snapshot_refresh: Passes
  • request_association: Not Assessed
Anthropic remote MCP fixture
Degraded
Transport behavior should match Claude-compatible HTTP expectations.
  • remote_transport: Passes
  • tool_discovery: Passes
  • auth_connect: Passes
  • safe_write_review: Degraded
Recommended for
Claude Desktop
Claude Desktop is marked compatible with score 83.
Smithery
Smithery is marked compatible with score 80.
Generic Streamable HTTP
Generic Streamable HTTP is marked compatible with score 100.
Healthcare claims workflows
Tool names and metadata indicate this server is oriented around healthcare claims use cases.

Evidence

Current trust snapshot
Snapshot ID
trustsnap_5818b3d2103e8cc1
Use this ID to compare server page, report, policy, MCP, homepage, ranking, and shortlist surfaces.
Snapshot generated
Aug 11, 2026 05:11:24 PM UTC
All page, report, policy, and MCP surfaces use this same server-detail snapshot shape.
Last validated
Aug 11, 2026 07:53:06 AM UTC
Age: 9.3h • evidence age tier: Verified in last 24h • display score: 54.69

Canonical machine links

Compare index
/compare.json
Compare API
/v1/compare?server=awesome-shieldzcash%2Fshieldz-mcp
Trust summary
/v1/servers/awesome-shieldzcash/shieldz-mcp/trust-summary
Report JSON
/v1/servers/awesome-shieldzcash/shieldz-mcp/report
Policy export
/v1/servers/awesome-shieldzcash/shieldz-mcp/policy
Badge metadata
/v1/servers/awesome-shieldzcash/shieldz-mcp/badge
Ledger evidence
/v1/servers/awesome-shieldzcash/shieldz-mcp/ledger
Human compare URL
/compare?server=awesome-shieldzcash%2Fshieldz-mcp
Evidence confidence
Confidence score
75.5
Based on 2 recent validations, 9 captured checks, and validation age of 9.3 hours.
Live checks captured
9
More direct checks increase trust in the current verdict.
Validation age
9.3h
Lower age means fresher evidence.
Latest validation evidence
Latest summary
Healthy
Validation profile
remote_mcp
Started
Aug 11, 2026 07:53:04 AM UTC
Latency
2548.1 ms

Failures

  • oauth_authorization_server no authorization server
  • oauth_protected_resource Client error '404 Not Found' for url 'https://shieldz.cash/.well-known/oauth-protected-resource' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
  • openid_configuration no authorization server
  • server_card Client error '404 Not Found' for url 'https://shieldz.cash/.well-known/mcp/server-card.json' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
  • transport_compliance_probe Issues: missing session id, missing protocol header, bad protocol not rejected (bad protocol=200).

Checks

CheckStatusLatencyEvidence
action_safety_probe Error n/a 2 high-risk, 1 exec-capable, non-read capabilities: write, exec, financial tool(s); no clear auth boundary; safeguards=0; confirmation=create tip jar.
advanced_capabilities_probe Missing n/a No advanced MCP capability signals detected.
connector_publishability_probe Warning n/a Publishability blockers: transport compliance, action safety, server card.
connector_replay_probe OK n/a Backward compatible with no breaking tool-surface changes.
determinism_probe OK 119.0 ms Check completed
initialize OK 136.1 ms Protocol 2025-03-26
interactive_flow_probe Missing n/a Check completed
oauth_authorization_server Missing n/a no authorization server
oauth_protected_resource Error 474.0 ms Client error '404 Not Found' for url 'https://shieldz.cash/.well-known/oauth-protected-resource' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
official_registry_probe Missing n/a Check completed
openid_configuration Missing n/a no authorization server
probe_noise_resilience OK 469.4 ms Fetched https://shieldz.cash/robots.txt
prompt_get Missing n/a not advertised
prompts_list Missing 115.5 ms not supported
protocol_version_probe Warning n/a Claims 2025-03-26; 2 release(s) behind 2025-11-25.
provenance_divergence_probe Not_Assessed n/a Check completed
request_association_probe Missing n/a No request-association capabilities were advertised.
resource_read Missing n/a not advertised
resources_list Missing 114.2 ms not supported
schema_divergence_probe Missing n/a no server card tools
server_card Error 332.4 ms Client error '404 Not Found' for url 'https://shieldz.cash/.well-known/mcp/server-card.json' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
session_resume_probe Warning n/a no session id
step_up_auth_probe Missing n/a No OAuth or incremental-scope signals detected.
tool_snapshot_probe OK n/a Check completed
tools_list OK 330.1 ms 3 tool(s) exposed
transport_compliance_probe Error 117.2 ms Issues: missing session id, missing protocol header, bad protocol not rejected (bad protocol=200).
utility_coverage_probe Missing 114.4 ms No completions evidence; no pagination evidence; tasks missing.
Known versions
  • No versions recorded.
Public server reputation
Validation success 7d
1.0
Validation success 30d
1.0
Mean time to recover
n/a
Breaking diffs 30d
0
Registry drift frequency 30d
0
Snapshot changes 30d
0
Benchmark tasks
Benchmark taskStatusEvidence
Discover tools Passes
  • initialize • OK
  • tools_list • OK
Read-only fetch flow Likely to fail
  • resource_read • Missing
  • read_only_tool_surface • Missing
OAuth-required connect Degraded
  • oauth_protected_resource • Error
  • step_up_auth_probe • Missing
Safe write flow with confirmation Likely to fail
  • action_safety_probe • Error
Utility coverage
Probe status
Missing
Completions
not detected
Completion probe target: none
Pagination
not detected
No nextCursor evidence.
Tasks
Missing
Advertised: no
Tool snapshot diff & changelog
Snapshot changed
no
Added tools
none
Removed tools
none
Required-argument changes
ToolAdded required argsRemoved required args
No required-argument changes detected.
Output-schema drift
ToolPrevious propertiesLatest properties
No output-schema drift detected.
Validation diff
Score delta
0
Summary changed
no
Tool delta
0
Prompt delta
0
Auth mode changed
no
Write surface expanded
no
Protocol regressed
no
Registry drift changed
no

Regressed checks: none

Improved checks: none

Newly assessed dimensions: none

No longer assessed dimensions: none

ComponentPreviousLatestDelta
No component deltas between the latest two runs.
Registry & provenance divergence
Probe status
Not_Assessed
Direct official match
no
Drift fields
none
Cross-registry alias disagreements
Error registry_source remote_url homepage registry_identifier
FieldRegistryLive server card
Titlen/an/a
Versionn/an/a
Homepagen/an/a
Active alerts

No active alerts for the current server state.

Aliases & registry graph
IdentifierSourceCanonicalIdentity evidenceScore
awesome-shieldzcash/shieldz-mcp awesome_mcp_servers yes canonical 54.7
ShieldZCash/shieldz-mcp glama_registry no repo_slug n/a
Alias consolidation

Strong alias identity requires matching remote URL, server-card URL, repository slug, or explicit registry cross-reference; shared provider namespace alone is not identity.

Canonical identifier
awesome-shieldzcash/shieldz-mcp
Duplicate aliases
1
Registry sources
awesome_mcp_servers glama_registry
Remote URLs
Homepages
Source disagreements
FieldWhat differsObserved values
Registry source Multiple registries or registry sync paths claim this same canonical server. awesome_mcp_servers glama_registry
Remote URL Aliases currently point at different MCP endpoints, which can indicate mirrors, stale registry data, or a real endpoint split. https://glama.ai/mcp/servers/sh6orevwl0 https://shieldz.cash/mcp
Homepage Registry entries disagree on the primary homepage for this server. https://github.com/ShieldZCash/shieldz-mcp https://glama.ai/mcp/servers/sh6orevwl0
Registry identifier Different registry-specific identifiers resolve to the same canonical server record here. awesome_mcp_servers:ShieldZCash/shieldz-mcp glama_registry:sh6orevwl0

Fix it

Why this score?
Access & Protocol
20/44
Connectivity, auth, and transport expectations for common clients.
Interface Quality
27/56
How well the tool/resource interface communicates and behaves under automation.
Security Posture
19/36
How safely the exposed tool surface handles destructive actions, egress, execution, secrets, and risky inputs.
Reliability & Trust
22/24
Operational stability, consistency, and trustworthiness over time.
Discovery & Governance
12/28
How well the server is documented, listed, and governed in public registries.
Adoption & Market
5/8
Adoption clues and public evidence that the server is intended for external use.
Algorithmic score breakdown
Auth Operability
2/4
Measures whether auth discovery and protected access behave predictably for clients.
Error Contract Quality
1/4
Grades machine-readable error structure, status alignment, and remediation hints.
Rate-Limit Semantics
2/4
Checks whether quota/throttle responses are deterministic and automation-friendly.
Schema Completeness
2/4
Completeness of tool descriptions, parameter docs, examples, and schema shape.
Backward Compatibility
4/4
Stability score across tool schema/name drift relative to prior validations.
SLO Health
3/4
Availability, latency, and burst-failure profile across recent validation history.
Security Hygiene
2/4
HTTPS posture, endpoint hygiene, and response-surface hardening checks.
Task Success
4/4
Can an agent reliably initialize, enumerate tools, and execute core MCP flows?
Trust Confidence
3/4
Confidence-adjusted reliability score that penalizes low evidence volume.
Abuse/Noise Resilience
4/4
How well the server preserves core behavior in the presence of noisy traffic patterns.
Prompt Contract
0/4
Quality of prompt metadata, argument shape, and prompt discoverability for clients.
Resource Contract
0/4
How completely resources and resource templates describe URIs, types, and usage shape.
Discovery Metadata
2/4
Homepage, docs, icon, repository, support, and license coverage for directory consumers.
Registry Consistency
2/4
Agreement between stored registry metadata, live server-card data, and current validation output.
Installability
4/4
How cleanly a real client can connect, initialize, enumerate tools, and proceed through auth.
Session Semantics
4/4
Determinism and state behavior across repeated MCP calls, including sticky-session surprises.
Tool Surface Design
3/4
Naming clarity, schema ergonomics, and parameter complexity across the tool surface.
Result Shape Stability
3/4
Stability of declared output schemas across validations, with penalties for drift or missing shapes.
OAuth Interop
0/4
Depth and client compatibility of OAuth/OIDC metadata beyond the minimal protected-resource check.
Recovery Semantics
0/4
Whether failures include actionable machine-readable next steps such as retry or upgrade guidance.
Maintenance Signal
3/4
Versioning, update recency, and historical validation cadence that indicate active stewardship.
Adoption Signal
2/4
Directory presence and distribution clues that suggest the server is intended for external use.
Freshness Confidence
4/4
Confidence that recent validations are current enough and dense enough to trust operationally.
Transport Fidelity
4/4
Whether declared transport metadata matches the observed endpoint behavior and response formats.
Spec Recency
2/4
How close the server’s claimed MCP protocol version is to the latest known public revision.
Session Resume
3/4
Whether Streamable HTTP session identifiers and resumed requests behave cleanly for real clients.
Step-Up Auth
0/4
Whether OAuth metadata and WWW-Authenticate challenges support granular, incremental consent instead of broad upfront scopes.
Transport Compliance
0/4
Checks session headers, protocol-version enforcement, session teardown, and expired-session behavior.
Utility Coverage
0/4
Signals support for completions, pagination, and task-oriented utility surfaces that larger clients increasingly expect.
Advanced Capability Coverage
0/4
Coverage of newer MCP surfaces like roots, sampling, elicitation, structured output, and related metadata.
Connector Publishability
3/4
How ready the server looks for client catalogs and managed connector programs.
Tool Snapshot Churn
4/4
Stability of the tool surface across recent validations, including add/remove and output-shape drift.
Connector Replay
4/4
Whether a previously published frozen connector snapshot would remain backward compatible after the latest tool refresh.
Request Association
0/4
Whether roots, sampling, and elicitation appear tied to active client requests instead of arriving unsolicited on idle sessions.
Interactive Flow Safety
0/4
Whether prompts and docs steer users toward safe auth flows instead of pasting secrets directly.
Action Safety
1/4
Risk-weighted view of destructive, exec, egress, and confirmation semantics across the tool surface.
Official Registry Presence
3/4
Whether the server appears directly or indirectly in the official MCP registry.
Safety Transparency
2/4
Clarity of docs, auth disclosure, support links, and other trust signals visible to integrators.
Tool Capability Clarity
4/4
How clearly the tool surface communicates whether each action reads, writes, deletes, executes, or exports data.
Destructive Operation Safety
3/4
Penalizes delete/revoke/destroy style tools unless auth and safeguards reduce blast radius.
Egress / SSRF Resilience
3/4
Assesses arbitrary URL fetch, crawl, webhook, and remote-request exposure on the tool surface.
Execution / Sandbox Safety
2/4
Evaluates shell, code, script, and command-execution exposure and whether that surface appears contained.
Data Exfiltration Resilience
3/4
Assesses export, dump, backup, and bulk-read behavior against the surrounding auth and safeguard signals.
Least Privilege Scope
1/4
Rewards scoped auth metadata and penalizes broad or missing scopes around privileged tools.
Secret Handling Hygiene
2/4
Assesses secret-bearing tools, token leakage risk, and whether the public surface avoids obvious secret exposure.
Supply Chain Signal
0/4
Public metadata signal for repository, changelog, license, versioning, and recency that supports supply-chain trust.
Input Sanitization Safety
3/4
Penalizes risky freeform string inputs when schemas do not constrain URLs, code, paths, queries, or templates.
Tool Namespace Clarity
4/4
Measures naming uniqueness and ambiguity across the tool namespace to reduce collision and confusion risk.

1 component(s) not assessed for this run: Provenance Divergence

Experimental candidate components
Personal Data Exposure
8.5
Experimental candidate, weight 0. Export and bulk-access evidence only; no impact on totals, verdicts, rankings, or gates.
Actionable remediation
SeverityRemediationWhy it mattersRecommended action
High Add confirmation and dry-run semantics for risky actions High-risk write, delete, exec, or egress tools should communicate safeguards clearly. Add an explicit confirm/dry-run parameter or two-step confirmation flow to write, delete, exec, and egress-capable tools before they can make destructive changes.
Playbook
  • For each high-risk tool (delete, exec, or network-egress capable), add a `confirm`/`dry_run` parameter or a two-step confirmation flow.
  • Document the safeguard in the tool's description so clients and agents know confirmation is required before execution.
  • Revalidate and confirm `action_safety_probe` reports the safeguard as detected.
High Align session and protocol behavior with Streamable HTTP expectations Clients increasingly rely on MCP-Protocol-Version, session teardown, and expired-session semantics. Align MCP-Protocol-Version, MCP-Session-Id, DELETE teardown, and expired-session handling with the transport spec.
Playbook
  • Return `Mcp-Session-Id` and `Mcp-Protocol-Version` headers consistently on streamable HTTP responses.
  • Honor `DELETE` session teardown and return `404` when a deleted session is reused.
  • Reject invalid protocol-version headers with `400 Bad Request`.
High Expose /.well-known/oauth-protected-resource Without a protected-resource document, OAuth clients cannot discover auth requirements reliably. Serve /.well-known/oauth-protected-resource and point it at your authorization server metadata.
Playbook
  • Serve `/.well-known/oauth-protected-resource` from the same host as the MCP endpoint.
  • Point it at the authorization server metadata URL.
  • Confirm clients receive consistent auth hints before tool execution.
High Publish OAuth authorization-server metadata Clients need authorization-server metadata to discover issuer, endpoints, and DCR support. Publish /.well-known/oauth-authorization-server from your issuer and include registration_endpoint when supported.
Playbook
  • Publish `/.well-known/oauth-authorization-server` from the issuer.
  • Add `registration_endpoint` if DCR is supported.
  • Verify issuer, authorization, token, and jwks metadata are all reachable.
High Publish a complete server card Missing or incomplete server-card metadata weakens discovery, documentation, and trust signals. Serve /.well-known/mcp/server-card.json and include tools, prompts/resources, homepage, and support links.
Playbook
  • Publish `/.well-known/mcp/server-card.json`.
  • Include homepage, repository, support, tools, prompts/resources, and auth metadata.
  • Revalidate the server after publishing the card.
Medium Adopt a current MCP protocol revision Older protocol revisions reduce compatibility with newer clients and registry programs. Advertise a current MCP protocol revision (2025-06-18 or later) in both the initialize response and the MCP-Protocol-Version header.
Playbook
  • Update the server's advertised protocol version to a current MCP revision (2025-06-18 or later).
  • Return the negotiated version consistently in both the `initialize` response and the `MCP-Protocol-Version` header.
  • Revalidate and confirm `protocol_version_probe` reports `ok`.
Medium Close connector-publishing gaps Connector catalogs care about protocol recency, session behavior, auth clarity, and tool-surface stability.
Medium Document minimal scopes and return cleaner auth challenges Modern clients expect granular scopes and step-up auth signals such as WWW-Authenticate scope hints. Return granular scopes and WWW-Authenticate challenge hints instead of forcing overly broad auth upfront.
Playbook
  • Advertise the narrowest viable scopes in OAuth metadata.
  • Return `WWW-Authenticate` challenges with scope or insufficient-scope hints when additional consent is needed.
  • Revalidate with both public discovery and auth-required flows.
Medium Publish OpenID configuration OIDC metadata improves token validation and client compatibility. Expose /.well-known/openid-configuration with issuer, jwks_uri, and supported grants.
Playbook
  • Serve `/.well-known/openid-configuration` with `issuer`, `jwks_uri`, `authorization_endpoint`, and `token_endpoint`.
  • List supported grant types in `grant_types_supported` and scopes in `scopes_supported`.
  • Revalidate and confirm the `openid_configuration` check returns `ok`.
Medium Support resumable HTTP sessions cleanly Modern MCP clients increasingly expect resumable session behavior on streamable HTTP transports. Persist session state keyed by Mcp-Session-Id and honor Last-Event-ID on GET reconnects so clients can resume a dropped Streamable HTTP session.
Playbook
  • Persist session state keyed by `Mcp-Session-Id` so a client can reconnect after a dropped connection.
  • Honor `Last-Event-ID` on GET reconnects to replay missed SSE events instead of erroring.
  • Revalidate and confirm `session_resume_probe` no longer returns `warning`.
Low Expose modern utility surfaces like completions, pagination, or tasks Utility coverage improves interoperability with larger clients and long-lived agent workflows. Expose completions, pagination, and task metadata where supported so larger clients can plan and resume work safely.
Playbook
  • Advertise `completions`, pagination cursors, and `tasks` only when they are actually supported.
  • Return `nextCursor` on large list operations when pagination is available.
  • Document task support and whether it requires step-up auth.
Low Publish newer MCP capability signals Roots, sampling, elicitation, structured outputs, and related metadata improve client understanding and ranking. Advertise only the advanced capabilities (roots, sampling, elicitation) you have actually implemented end to end in the initialize capabilities object.
Playbook
  • Add the capabilities you actually support (`roots`, `sampling`, `elicitation`) to the `capabilities` object returned from `initialize`.
  • Only advertise a capability once the corresponding request/response flow is implemented end to end.
  • Revalidate and confirm `advanced_capabilities_probe` reflects the updated capability set.
Low Publish or reconcile the server in the official MCP registry Official registry presence improves discovery confidence and cross-source consistency.
Point loss breakdown
ComponentCurrentPoints missing
Utility Coverage 0/4 -4.0
Transport Compliance 0/4 -4.0
Step Up Auth 0/4 -4.0
Resource Contract 0/4 -4.0
Request Association 0/4 -4.0
Recovery Semantics 0/4 -4.0
Prompt Contract 0/4 -4.0
OAUTH Interop 0/4 -4.0
Interactive Flow Safety 0/4 -4.0
Dependency Supply Chain Signal 0/4 -4.0
Advanced Capability Coverage 0/4 -4.0
Least Privilege Scope 1/4 -3.0
Compatibility profiles
OpenAI Connectors
55.6
partial (5 of 9 requirements met)
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Transport compliance failed or did not complete successfully.; OAuth interoperability should be strong.
Connector URL: https://shieldz.cash/mcp
# No OAuth metadata detected.
# Server: awesome-shieldzcash/shieldz-mcp
Claude Desktop
83.3
compatible (5 of 6 requirements met)
Transport behavior should match Claude-compatible HTTP expectations.
{
  "mcpServers": {
    "shieldz-mcp": {
      "command": "npx",
      "args": ["mcp-remote", "https://shieldz.cash/mcp"]
    }
  }
}
Smithery
80.0
compatible (4 of 5 requirements met)
Machine-readable failure semantics should be present.
smithery mcp add "https://shieldz.cash/mcp"
Generic Streamable HTTP
100.0
compatible (6 of 6 requirements met)
No major blockers detected.
curl -sS https://shieldz.cash/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'

Governance

MCP TrustOps

TrustOps turns this report into operational controls: freshness SLAs, authenticated validation, semantic benchmarks, policy exports, alert subscriptions, badges, cost/compliance metadata, and runtime routing. Fresh trusted index decisions stay separate from long-tail inventory so stale scores do not masquerade as current evidence.

Evidence age tier
Verified in last 24h
Policy SLA (contractual, distinct from the public 24h freshness window): 168.0h • confidence-weighted score (display score discounted for evidence age and confidence -- an internal TrustOps input, not the public score): 41.3 • evidence too old to display: ✕
Policy exports
Export policy
Formats: json, rego, yaml, github_action, gateway_config, client_report
Runtime routing
/v1/decide
Returns allowed tools, blocked tools, approval requirement, and reason.
Hosted runtime
Verify Hosted MCP
Deploy trusted servers from GitHub with secrets, egress controls, releases, rollback, and audit events.
Authenticated validation
✕
Premium publisher feature: paid authenticated runs verify scopes, write-action safeguards, and authorized tool execution.
Active trust badges
none
Semantic benchmarks
available
Templates cover GitHub, database, healthcare, web search, and CRM least-privilege jobs.
Supply chain
metadata signal
Deep scan checks are marked separately from public metadata signals.
Compliance metadata
✓
Terms, privacy, SOC 2, HIPAA, GDPR, retention, deletion, and audit-log fields are tracked as enterprise metadata.
Alert subscription types
Status changes Score drops or recovers Freshness SLA breach Validation schema drift OAuth or auth behavior changes Tool surface changes New or changed write tool Supply-chain signal changes Legal or compliance metadata changes
MCP Runtime hosting

Verify Hosted MCP turns a trusted server report into a managed remote MCP endpoint with GitHub deployment provenance, sandbox policy, encrypted secrets, release history, rollback, and audit/usage events.

Activation readiness
✕
Trusted hosted runtimes require fresh validation, a passing server state, a remote endpoint, and a minimum score.
Minimum tier
TrustOps
Publisher claim plus paid TrustOps tier are required before secrets or releases can be created.
Hosted endpoint
/hosted/{namespace}/{name}/mcp
The endpoint enforces egress allowlists and records audit/usage events.
Blockers
score_below_hosting_threshold blocked_by_production_readiness unsafe_write_action_surface
DeploymentStatusEndpointRelease
No hosted runtime deployments yet.
Authenticated validation sessions

Public validation is free. Authenticated validation is paid and proves scoped behavior, write-action safeguards, and authenticated tool execution.

Latest profile
remote_mcp
Authenticated session used
✕
Public score isolation
✓
Preview endpoint
/v1/verify
CI preview endpoint
/v1/ci/preview
Install snippets
Openai Connectors
Connector URL: https://shieldz.cash/mcp
# No OAuth metadata detected.
# Server: awesome-shieldzcash/shieldz-mcp
Claude Desktop
{
  "mcpServers": {
    "shieldz-mcp": {
      "command": "npx",
      "args": ["mcp-remote", "https://shieldz.cash/mcp"]
    }
  }
}
Smithery
smithery mcp add "https://shieldz.cash/mcp"
Generic Http
curl -sS https://shieldz.cash/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'
Agent access & tool surface
Live server tools
create_payment_link create_tip_jar get_account_status
Observed from the latest live validation against https://shieldz.cash/mcp. This is the target server surface, not Verify's own inspection tools.
Live capability counts
3 tools • 0 prompts • 0 resources
Counts come from the latest tools/list, prompts/list, and resources/list checks.
Inspect with Verify
search fetch search_servers recommend_servers get_server_report compare_servers
Use Verify itself to search, recommend, compare, and fetch the full report for awesome-shieldzcash/shieldz-mcp.
Direct machine links
JSON report • Compare this server • Verify MCP API

History

Validation history
7 day score delta
n/a
30 day score delta
n/a
Recent healthy ratio
100%
Freshness
9.3h
TimestampStatusScoreLatencyTools
Aug 11, 2026 07:53:06 AM UTC Healthy 54.7 2548.1 ms 3
Aug 10, 2026 07:52:52 PM UTC Healthy 54.7 3157.2 ms 3
Aug 10, 2026 07:52:26 AM UTC Healthy 54.7 3216.8 ms not fetched
Aug 09, 2026 07:52:16 PM UTC Healthy 54.7 3292.6 ms not fetched
Aug 09, 2026 07:52:09 AM UTC Healthy 54.7 3353.2 ms not fetched
Aug 08, 2026 07:51:20 PM UTC Healthy 54.2 2645.9 ms not fetched
Aug 08, 2026 07:50:58 AM UTC Healthy 53.6 2573.3 ms not fetched
Aug 07, 2026 07:50:41 PM UTC Healthy 53.6 7761.0 ms not fetched
Validation timeline
ValidatedSummaryScoreProtocolAuth modeToolsHigh-risk toolsChanges
Aug 11, 2026 07:53:06 AM UTC Healthy 54.7 2025-03-26 public 3 2 none
Aug 10, 2026 07:52:52 PM UTC Healthy 54.7 2025-03-26 public 3 2 none
Aug 10, 2026 07:52:26 AM UTC Healthy n/a unknown unknown not fetched 0 none
Aug 09, 2026 07:52:16 PM UTC Healthy n/a unknown unknown not fetched 0 none
Aug 09, 2026 07:52:09 AM UTC Healthy n/a unknown unknown not fetched 0 none
Aug 08, 2026 07:51:20 PM UTC Healthy n/a unknown unknown not fetched 0 none
Aug 08, 2026 07:50:58 AM UTC Healthy n/a unknown unknown not fetched 0 none
Aug 07, 2026 07:50:41 PM UTC Healthy n/a unknown unknown not fetched 0 none
Aug 07, 2026 07:50:18 AM UTC Healthy n/a unknown unknown not fetched 0 none
Aug 06, 2026 07:49:59 PM UTC Healthy n/a unknown unknown not fetched 0 none
Recent validation runs
Recent validation runs for this MCP server
StartedStatusSummaryLatencyChecks
Aug 11, 2026 07:53:04 AM UTC Completed Healthy 2548.1 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, schema_divergence_probe, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
Aug 10, 2026 07:52:48 PM UTC Completed Healthy 3157.2 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, schema_divergence_probe, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
Aug 10, 2026 07:52:23 AM UTC Completed Healthy 3216.8 ms not fetched (not counted in confidence)
Aug 09, 2026 07:52:12 PM UTC Completed Healthy 3292.6 ms not fetched (not counted in confidence)
Aug 09, 2026 07:52:05 AM UTC Completed Healthy 3353.2 ms not fetched (not counted in confidence)
Aug 08, 2026 07:51:18 PM UTC Completed Healthy 2645.9 ms not fetched (not counted in confidence)
Aug 08, 2026 07:50:55 AM UTC Completed Healthy 2573.3 ms not fetched (not counted in confidence)
Aug 07, 2026 07:50:34 PM UTC Completed Healthy 7761.0 ms not fetched (not counted in confidence)
Aug 07, 2026 07:50:15 AM UTC Completed Healthy 3154.6 ms not fetched (not counted in confidence)
Aug 06, 2026 07:49:56 PM UTC Completed Healthy 3240.8 ms not fetched (not counted in confidence)
Incident & change feed
TimestampEventDetails
Aug 11, 2026 07:53:06 AM UTC Latest validation: healthy Score 54.7 with status healthy.
Aug 05, 2026 10:58:20 AM UTC Score corrected (post-1.0.503 remediation, R1 zero-anchoring) Prior: 68.67. Corrected: 64.9.

Technical details

Raw evidence view
Show raw JSON evidence 
{
  "checks": {
    "action_safety_probe": {
      "details": {
        "auth_present": false,
        "confirmation_signals": [
          "create_tip_jar"
        ],
        "reason": null,
        "safeguard_count": 0,
        "summary": {
          "annotation_conflict_tools": 0,
          "bulk_access_tools": 0,
          "capability_distribution": {
            "exec": 1,
            "financial": 2,
            "read": 2,
            "secrets": 1,
            "write": 3
          },
          "declared_non_read_only_tools": 0,
          "destructive_tools": 0,
          "egress_tools": 0,
          "exec_tools": 1,
          "has_mutating_capability": true,
          "has_non_read_capability": true,
          "high_risk_tools": 2,
          "risk_distribution": {
            "critical": 1,
            "high": 1,
            "low": 0,
            "medium": 1
          },
          "secret_tools": 1,
          "tool_count": 3
        }
      },
      "latency_ms": null,
      "status": "error"
    },
    "advanced_capabilities_probe": {
      "details": {
        "capabilities": {
          "completions": false,
          "elicitation": false,
          "prompts": false,
          "resource_links": false,
          "resources": false,
          "roots": false,
          "sampling": false,
          "structured_outputs": false
        },
        "enabled": [],
        "enabled_count": 0,
        "initialize_capability_keys": [
          "tools"
        ]
      },
      "latency_ms": null,
      "status": "missing"
    },
    "connector_publishability_probe": {
      "details": {
        "blockers": [
          "transport_compliance",
          "action_safety",
          "server_card"
        ],
        "criteria": {
          "action_safety": false,
          "auth_flow": true,
          "connector_replay": true,
          "initialize": true,
          "protocol_version": true,
          "remote_transport": true,
          "request_association": true,
          "server_card": false,
          "session_resume": true,
          "step_up_auth": true,
          "tool_surface": true,
          "tools_list": true,
          "transport_compliance": false
        },
        "high_risk_tools": 2,
        "tool_count": 3,
        "transport": "streamable-http"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "connector_replay_probe": {
      "details": {
        "added_tools": [],
        "additive_output_changes": [],
        "backward_compatible": true,
        "output_breaks": [],
        "removed_tools": [],
        "required_arg_breaks": [],
        "would_break_after_refresh": false
      },
      "latency_ms": null,
      "status": "ok"
    },
    "determinism_probe": {
      "details": {
        "attempts": 2,
        "baseline_signature": "4d74c8bfea74863ea192a5c75766e8cd8c2d957c8aa65260aa66326483d948de",
        "errors": [],
        "matches": 2,
        "stable_ratio": 1.0,
        "successful": 2
      },
      "latency_ms": 118.99,
      "status": "ok"
    },
    "initialize": {
      "details": {
        "headers": {
          "content-type": "application/json"
        },
        "http_status": 200,
        "payload": {
          "id": 1,
          "jsonrpc": "2.0",
          "result": {
            "capabilities": {
              "tools": {
                "listChanged": false
              }
            },
            "instructions": "Keyless, non-custodial crypto payments. create_payment_link and create_tip_jar need only a wallet address; no API key.",
            "protocolVersion": "2025-03-26",
            "serverInfo": {
              "name": "shieldz",
              "version": "0.3.0"
            }
          }
        },
        "url": "https://shieldz.cash/mcp"
      },
      "latency_ms": 136.13,
      "status": "ok"
    },
    "interactive_flow_probe": {
      "details": {
        "oauth_supported": false,
        "prompt_available": false,
        "risk_hits": [],
        "safe_hits": []
      },
      "latency_ms": null,
      "status": "missing"
    },
    "oauth_authorization_server": {
      "details": {
        "reason": "no_authorization_server"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "oauth_protected_resource": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://shieldz.cash/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "url": "https://shieldz.cash/.well-known/oauth-protected-resource"
      },
      "latency_ms": 473.96,
      "status": "error"
    },
    "official_registry_probe": {
      "details": {
        "direct_match": false,
        "official_peer_count": 0,
        "registry_source": "awesome_mcp_servers"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "openid_configuration": {
      "details": {
        "reason": "no_authorization_server"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "probe_noise_resilience": {
      "details": {
        "consent_error": null,
        "headers": {
          "content-type": "text/plain; charset=utf-8"
        },
        "http_status": 200,
        "url": "https://shieldz.cash/robots.txt",
        "validation_disallowed": false
      },
      "latency_ms": 469.38,
      "status": "ok"
    },
    "prompt_get": {
      "details": {
        "reason": "not_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "prompts_list": {
      "details": {
        "headers": {
          "content-type": "application/json"
        },
        "http_status": 200,
        "payload": {
          "error": {
            "code": -32601,
            "message": "Method not found: prompts/list"
          },
          "id": 3,
          "jsonrpc": "2.0"
        },
        "reason": "not_supported",
        "url": "https://shieldz.cash/mcp"
      },
      "latency_ms": 115.55,
      "status": "missing"
    },
    "protocol_version_probe": {
      "details": {
        "claimed_version": "2025-03-26",
        "lag_days": 244,
        "latest_known_version": "2025-11-25",
        "releases_behind": 2,
        "validator_protocol_version": "2025-03-26"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "provenance_divergence_probe": {
      "details": {
        "comparable_field_count": 0,
        "compared_fields": [
          "title",
          "version",
          "homepage",
          "repository"
        ],
        "direct_official_match": false,
        "drift_fields": [],
        "metadata_document_count": 1,
        "readable_sources": [],
        "registry_homepage": null,
        "registry_repository": null,
        "registry_title": null,
        "registry_version": null,
        "server_card_homepage": null,
        "server_card_repository": null,
        "server_card_title": null,
        "server_card_version": null
      },
      "latency_ms": null,
      "status": "not_assessed"
    },
    "request_association_probe": {
      "details": {
        "reason": "no_request_association_capabilities_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "resource_read": {
      "details": {
        "reason": "not_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "resources_list": {
      "details": {
        "headers": {
          "content-type": "application/json"
        },
        "http_status": 200,
        "payload": {
          "error": {
            "code": -32601,
            "message": "Method not found: resources/list"
          },
          "id": 5,
          "jsonrpc": "2.0"
        },
        "reason": "not_supported",
        "url": "https://shieldz.cash/mcp"
      },
      "latency_ms": 114.19,
      "status": "missing"
    },
    "schema_divergence_probe": {
      "details": {
        "auth_scheme_mismatch": false,
        "card_server_name": null,
        "card_server_version": null,
        "compared_dimensions": [
          "server_name",
          "server_version",
          "declared_vs_observed_auth",
          "tool_membership",
          "parameter_names",
          "required_parameters",
          "parameter_types",
          "output_schema_presence"
        ],
        "compared_tool_count": 0,
        "live_server_name": "shieldz",
        "live_server_version": "0.3.0",
        "reason": "no_server_card_tools",
        "server_name_mismatch": false,
        "server_version_mismatch": false
      },
      "latency_ms": null,
      "status": "missing"
    },
    "server_card": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://shieldz.cash/.well-known/mcp/server-card.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "url": "https://shieldz.cash/.well-known/mcp/server-card.json"
      },
      "latency_ms": 332.44,
      "status": "error"
    },
    "session_resume_probe": {
      "details": {
        "protocol_version": "2025-03-26",
        "reason": "no_session_id",
        "resume_expected": true,
        "transport": "streamable-http"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "step_up_auth_probe": {
      "details": {
        "auth_required_checks": [],
        "broad_scopes": [],
        "challenge_headers": [],
        "minimal_scope_documented": false,
        "oauth_present": false,
        "scope_specificity_ratio": 0.0,
        "step_up_signals": [],
        "supported_scopes": []
      },
      "latency_ms": null,
      "status": "missing"
    },
    "tool_snapshot_probe": {
      "details": {
        "added": [],
        "changed_outputs": [],
        "current_tool_count": 3,
        "previous_tool_count": 3,
        "removed": [],
        "similarity": 1.0
      },
      "latency_ms": null,
      "status": "ok"
    },
    "tools_list": {
      "details": {
        "headers": {
          "content-type": "application/json"
        },
        "http_status": 200,
        "payload": {
          "id": 2,
          "jsonrpc": "2.0",
          "result": {
            "tools": [
              {
                "description": "Create a one-time crypto payment link with ZERO setup, no account, no API key. Give a destination wallet address and an amount; get back a shareable pay_url, an embeddable button, and a manage_url. Non-custodial: funds settle directly to the address you provide.",
                "inputSchema": {
                  "properties": {
                    "address": {
                      "description": "Destination wallet (0x EVM address); funds settle here.",
                      "type": "string"
                    },
                    "amount_usd": {
                      "description": "Amount in USD, e.g. 49 for $49.00",
                      "type": "number"
                    },
                    "asset": {
                      "description": "Stablecoin (default USDC)",
                      "enum": [
                        "USDC",
                        "USDT"
                      ],
                      "type": "string"
                    },
                    "chain": {
                      "description": "Settlement chain (default base)",
                      "enum": [
                        "base",
                        "arbitrum",
                        "optimism",
                        "polygon",
                        "ethereum"
                      ],
                      "type": "string"
                    },
                    "email": {
                      "description": "Optional, lets the owner claim a dashboard later",
                      "type": "string"
                    },
                    "memo": {
                      "description": "Description shown on the checkout",
                      "type": "string"
                    }
                  },
                  "required": [
                    "address",
                    "amount_usd"
                  ],
                  "type": "object"
                },
                "name": "create_payment_link"
              },
              {
                "description": "Create a reusable 'pay what you want' tip jar with ZERO setup. The payer chooses the amount. Returns a shareable /tip url, an embeddable button, and a manage_url. Idempotent per wallet address. Non-custodial.",
                "inputSchema": {
                  "properties": {
                    "address": {
                      "description": "Destination wallet (0x EVM address); funds settle here.",
                      "type": "string"
                    },
                    "asset": {
                      "description": "Stablecoin (default USDC)",
                      "enum": [
                        "USDC",
                        "USDT"
                      ],
                      "type": "string"
                    },
                    "chain": {
                      "description": "Settlement chain (default base)",
                      "enum": [
                        "base",
                        "arbitrum",
                        "optimism",
                        "polygon",
                        "ethereum"
                      ],
                      "type": "string"
                    },
                    "description": {
                      "type": "string"
                    },
                    "email": {
                      "description": "Optional, lets the owner claim a dashboard later",
                      "type": "string"
                    },
                    "slug": {
                      "description": "Optional custom URL slug",
                      "type": "string"
                    },
                    "suggested_amounts_usd": {
                      "description": "Preset amount buttons in USD, e.g. [3, 5, 10]",
                      "items": {
                        "type": "number"
                      },
                      "type": "array"
                    },
                    "title": {
                      "description": "Heading shown on the tip page, e.g. 'Buy me a coffee'",
                      "type": "string"
                    }
                  },
                  "required": [
                    "address"
                  ],
                  "type": "object"
                },
                "name": "create_tip_jar"
              },
              {
                "description": "Look up a keyless Shieldz account by its manage_token (returned when you create a payment link or tip jar). Returns settlement details, tip jars, totals (paid/pending), and the invoice list as structured JSON.",
                "inputSchema": {
                  "properties": {
                    "manage_token": {
                      "description": "The manage_token from create_payment_link / create_tip_jar",
                      "type": "string"
                    }
                  },
                  "required": [
                    "manage_token"
                  ],
                  "type": "object"
                },
                "name": "get_account_status"
              }
            ]
          }
        },
        "url": "https://shieldz.cash/mcp"
      },
      "latency_ms": 330.15,
      "status": "ok"
    },
    "transport_compliance_probe": {
      "details": {
        "bad_protocol_error": null,
        "bad_protocol_headers": {
          "content-type": "application/json"
        },
        "bad_protocol_payload": {
          "id": 410,
          "jsonrpc": "2.0",
          "result": {
            "tools": [
              {
                "description": "Create a one-time crypto payment link with ZERO setup, no account, no API key. Give a destination wallet address and an amount; get back a shareable pay_url, an embeddable button, and a manage_url. Non-custodial: funds settle directly to the address you provide.",
                "inputSchema": {
                  "properties": {
                    "address": {
                      "description": "Destination wallet (0x EVM address); funds settle here.",
                      "type": "string"
                    },
                    "amount_usd": {
                      "description": "Amount in USD, e.g. 49 for $49.00",
                      "type": "number"
                    },
                    "asset": {
                      "description": "Stablecoin (default USDC)",
                      "enum": [
                        "USDC",
                        "USDT"
                      ],
                      "type": "string"
                    },
                    "chain": {
                      "description": "Settlement chain (default base)",
                      "enum": [
                        "base",
                        "arbitrum",
                        "optimism",
                        "polygon",
                        "ethereum"
                      ],
                      "type": "string"
                    },
                    "email": {
                      "description": "Optional, lets the owner claim a dashboard later",
                      "type": "string"
                    },
                    "memo": {
                      "description": "Description shown on the checkout",
                      "type": "string"
                    }
                  },
                  "required": [
                    "address",
                    "amount_usd"
                  ],
                  "type": "object"
                },
                "name": "create_payment_link"
              },
              {
                "description": "Create a reusable 'pay what you want' tip jar with ZERO setup. The payer chooses the amount. Returns a shareable /tip url, an embeddable button, and a manage_url. Idempotent per wallet address. Non-custodial.",
                "inputSchema": {
                  "properties": {
                    "address": {
                      "description": "Destination wallet (0x EVM address); funds settle here.",
                      "type": "string"
                    },
                    "asset": {
                      "description": "Stablecoin (default USDC)",
                      "enum": [
                        "USDC",
                        "USDT"
                      ],
                      "type": "string"
                    },
                    "chain": {
                      "description": "Settlement chain (default base)",
                      "enum": [
                        "base",
                        "arbitrum",
                        "optimism",
                        "polygon",
                        "ethereum"
                      ],
                      "type": "string"
                    },
                    "description": {
                      "type": "string"
                    },
                    "email": {
                      "description": "Optional, lets the owner claim a dashboard later",
                      "type": "string"
                    },
                    "slug": {
                      "description": "Optional custom URL slug",
                      "type": "string"
                    },
                    "suggested_amounts_usd": {
                      "description": "Preset amount buttons in USD, e.g. [3, 5, 10]",
                      "items": {
                        "type": "number"
                      },
                      "type": "array"
                    },
                    "title": {
                      "description": "Heading shown on the tip page, e.g. 'Buy me a coffee'",
                      "type": "string"
                    }
                  },
                  "required": [
                    "address"
                  ],
                  "type": "object"
                },
                "name": "create_tip_jar"
              },
              {
                "description": "Look up a keyless Shieldz account by its manage_token (returned when you create a payment link or tip jar). Returns settlement details, tip jars, totals (paid/pending), and the invoice list as structured JSON.",
                "inputSchema": {
                  "properties": {
                    "manage_token": {
                      "description": "The manage_token from create_payment_link / create_tip_jar",
                      "type": "string"
                    }
                  },
                  "required": [
                    "manage_token"
                  ],
                  "type": "object"
                },
                "name": "get_account_status"
              }
            ]
          }
        },
        "bad_protocol_status_code": 200,
        "delete_error": null,
        "delete_status_code": null,
        "expired_session_error": null,
        "expired_session_status_code": null,
        "issues": [
          "missing_session_id",
          "missing_protocol_header",
          "bad_protocol_not_rejected"
        ],
        "last_event_id_visible": false,
        "protocol_header_present": false,
        "requested_protocol_version": "2025-03-26",
        "session_id_present": false,
        "transport": "streamable-http"
      },
      "latency_ms": 117.15,
      "status": "error"
    },
    "utility_coverage_probe": {
      "details": {
        "completions": {
          "advertised": false,
          "live_probe": "not_executed",
          "sample_target": null
        },
        "initialize_capability_keys": [
          "tools"
        ],
        "pagination": {
          "metadata_signal": false,
          "next_cursor_methods": [],
          "supported": false
        },
        "tasks": {
          "advertised": false,
          "http_status": 200,
          "probe_status": "missing"
        }
      },
      "latency_ms": 114.41,
      "status": "missing"
    }
  },
  "failures": {
    "oauth_authorization_server": {
      "reason": "no_authorization_server"
    },
    "oauth_protected_resource": {
      "error": "Client error '404 Not Found' for url 'https://shieldz.cash/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
      "url": "https://shieldz.cash/.well-known/oauth-protected-resource"
    },
    "openid_configuration": {
      "reason": "no_authorization_server"
    },
    "server_card": {
      "error": "Client error '404 Not Found' for url 'https://shieldz.cash/.well-known/mcp/server-card.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
      "url": "https://shieldz.cash/.well-known/mcp/server-card.json"
    },
    "transport_compliance_probe": {
      "bad_protocol_error": null,
      "bad_protocol_headers": {
        "content-type": "application/json"
      },
      "bad_protocol_payload": {
        "id": 410,
        "jsonrpc": "2.0",
        "result": {
          "tools": [
            {
              "description": "Create a one-time crypto payment link with ZERO setup, no account, no API key. Give a destination wallet address and an amount; get back a shareable pay_url, an embeddable button, and a manage_url. Non-custodial: funds settle directly to the address you provide.",
              "inputSchema": {
                "properties": {
                  "address": {
                    "description": "Destination wallet (0x EVM address); funds settle here.",
                    "type": "string"
                  },
                  "amount_usd": {
                    "description": "Amount in USD, e.g. 49 for $49.00",
                    "type": "number"
                  },
                  "asset": {
                    "description": "Stablecoin (default USDC)",
                    "enum": [
                      "USDC",
                      "USDT"
                    ],
                    "type": "string"
                  },
                  "chain": {
                    "description": "Settlement chain (default base)",
                    "enum": [
                      "base",
                      "arbitrum",
                      "optimism",
                      "polygon",
                      "ethereum"
                    ],
                    "type": "string"
                  },
                  "email": {
                    "description": "Optional, lets the owner claim a dashboard later",
                    "type": "string"
                  },
                  "memo": {
                    "description": "Description shown on the checkout",
                    "type": "string"
                  }
                },
                "required": [
                  "address",
                  "amount_usd"
                ],
                "type": "object"
              },
              "name": "create_payment_link"
            },
            {
              "description": "Create a reusable 'pay what you want' tip jar with ZERO setup. The payer chooses the amount. Returns a shareable /tip url, an embeddable button, and a manage_url. Idempotent per wallet address. Non-custodial.",
              "inputSchema": {
                "properties": {
                  "address": {
                    "description": "Destination wallet (0x EVM address); funds settle here.",
                    "type": "string"
                  },
                  "asset": {
                    "description": "Stablecoin (default USDC)",
                    "enum": [
                      "USDC",
                      "USDT"
                    ],
                    "type": "string"
                  },
                  "chain": {
                    "description": "Settlement chain (default base)",
                    "enum": [
                      "base",
                      "arbitrum",
                      "optimism",
                      "polygon",
                      "ethereum"
                    ],
                    "type": "string"
                  },
                  "description": {
                    "type": "string"
                  },
                  "email": {
                    "description": "Optional, lets the owner claim a dashboard later",
                    "type": "string"
                  },
                  "slug": {
                    "description": "Optional custom URL slug",
                    "type": "string"
                  },
                  "suggested_amounts_usd": {
                    "description": "Preset amount buttons in USD, e.g. [3, 5, 10]",
                    "items": {
                      "type": "number"
                    },
                    "type": "array"
                  },
                  "title": {
                    "description": "Heading shown on the tip page, e.g. 'Buy me a coffee'",
                    "type": "string"
                  }
                },
                "required": [
                  "address"
                ],
                "type": "object"
              },
              "name": "create_tip_jar"
            },
            {
              "description": "Look up a keyless Shieldz account by its manage_token (returned when you create a payment link or tip jar). Returns settlement details, tip jars, totals (paid/pending), and the invoice list as structured JSON.",
              "inputSchema": {
                "properties": {
                  "manage_token": {
                    "description": "The manage_token from create_payment_link / create_tip_jar",
                    "type": "string"
                  }
                },
                "required": [
                  "manage_token"
                ],
                "type": "object"
              },
              "name": "get_account_status"
            }
          ]
        }
      },
      "bad_protocol_status_code": 200,
      "delete_error": null,
      "delete_status_code": null,
      "expired_session_error": null,
      "expired_session_status_code": null,
      "issues": [
        "missing_session_id",
        "missing_protocol_header",
        "bad_protocol_not_rejected"
      ],
      "last_event_id_visible": false,
      "protocol_header_present": false,
      "requested_protocol_version": "2025-03-26",
      "session_id_present": false,
      "transport": "streamable-http"
    }
  },
  "remote_url": "https://shieldz.cash/mcp",
  "server_card_payload": null,
  "server_identifier": "awesome-shieldzcash/shieldz-mcp"
}
Capabilities
Use-case taxonomy
finance healthcare
Transport compliance drilldown
Probe status
Error
Transport
streamable-http
Session header
no
Protocol header
no
Bad protocol response
200
DELETE teardown
n/a
Expired session retry
n/a
Last-Event-ID visible
no

Issues: missing_session_id, missing_protocol_header, bad_protocol_not_rejected

Request association
Status
Missing
Advertised capabilities
none
Observed idle methods
none
Violating methods
none
Probe HTTP status
n/a
Issues
none
Connector replay
Status
OK
Backward compatible
✓
Would break after refresh
✕
Added tools
none
Removed tools
none
Additive output changes
none
Required-argument replay breaks
ToolAdded required argsRemoved required args
No required-argument replay breaks detected.
Output-schema replay breaks
ToolRemoved propertiesAdded properties
No output-schema replay breaks detected.