sh.agentcard/agentcard
REMOTE · MCP.AGENTCARD.SH · SCANNED AUG 3
Prepaid virtual cards for AI agents: one-time cards, spend caps, human approvals.
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 →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability54
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 7861 tokens (~157/item across 50 items; 50 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.agentcard.sh
claude mcp add --transport http sh-agentcard-agentcard https://mcp.agentcard.sh/mcp
[mcp_servers.sh-agentcard-agentcard] url = "https://mcp.agentcard.sh/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sh-agentcard-agentcard": {
"type": "remote",
"url": "https://mcp.agentcard.sh/mcp",
"enabled": true
}
}
} openclaw mcp add sh-agentcard-agentcard --url https://mcp.agentcard.sh/mcp --transport streamable-http
mcp_servers:
sh-agentcard-agentcard:
url: "https://mcp.agentcard.sh/mcp" {
"mcpServers": {
"sh-agentcard-agentcard": {
"type": "http",
"url": "https://mcp.agentcard.sh/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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +6
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +42
- HSTS header: pass → fail ▼ security
- Transport: unverified → pass ▲ security
- Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
- 27 Jul 26 +21
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 3
First indexed and scored.
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 3 Aug 2026 · Probed https://mcp.agentcard.sh/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.agentcard.sh | CN=WE1,O=Google Trust Services,C=US | 26 Jul 2026 | 24 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | c7c62f1e2c602fc60e2e1649875e2365 |
| SANs: mcp.agentcard.sh | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of mcp.agentcard.sh. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| sh. | present | 55297 | 8 | Verified |
| agentcard.sh. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.agentcard.sh/.well-known/oauth-protected-resource/mcp"
Bearer resource_metadata="https://mcp.agentcard.sh/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://mcp.agentcard.sh/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.agentcard.sh/mcp |
| Authorisation server | https://mcp.agentcard.sh/ |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.agentcard.sh/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.agentcard.sh/mcp | HTTPS enforced | 301 | https://mcp.agentcard.sh/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.
whoami ~123
Show who you are operating as: the authenticated AgentCard account's email, user id, name, plan, KYC + account status, member-since date, and how this session is connected (personal login vs a third-party OAuth app connection, with the app name). Call this when the user asks "who am I" / "which account is this", or before money-moving actions when you need to confirm the account. Read-only. KYC shown here is the stored snapshot — use get_kyc_status when you need the live, provider-checked state.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| accountStatus | string | — | Account standing: 'active' or 'suspended'. |
| connectionClientId | string|null | — | OAuth client id of the connected app, when connectionType is oauth. |
| connectionClientName | string|null | — | Display name of the connected OAuth app (e.g. "Claude"), when known. |
| connectionOrganizationId | string|null | — | Organization id, when connectionType is organization. |
| connectionType | string | — | How this session authenticates: 'oauth' (third-party app connection), 'personal' (CLI/dashboard login), or 'organization' (a company's Agentcard integration acting for its end user). |
| string|null | — | Email of the authenticated account, or null for a phone-first account (e.g. signed up by SMS on the iMessage relay). | |
| kycStatus | string|null | — | Raw stored KYC state (e.g. approved, pending, requires_input), or null if never started. |
| kycVerified | boolean | — | Whether identity verification (KYC) has passed (stored snapshot). |
| memberSince | string | — | ISO timestamp the account was created. |
| message | string | yes | Human-readable identity summary. |
| name | string|null | — | Cardholder name ("First Last"), or null before KYC info is submitted. |
| plan | string | — | Subscription plan id, e.g. 'free', 'basic', or 'pro'. |
| subscriptionStatus | string|null | — | Stripe subscription status (e.g. 'active', 'past_due'), or null on the free plan. |
| userId | string | — | AgentCard user id of the authenticated account. |
No examples provided.
withdraw ~220
Withdraw cash from the user's balance, either to their saved bank account or to a crypto address on Base (USDC). Transfers are processed manually by the Agentcard team, usually within 1-3 business days; the user is emailed when it's sent. For a bank withdrawal, if the user has no saved bank account yet, call create_withdrawal_recipient first. For a crypto withdrawal, pass destination_address (a 0x Base address). ALWAYS confirm the amount and destination with the user before calling this.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_cents | number | yes | Amount to withdraw in cents (e.g. 2500 = $25.00). Range: $2.00 to $10,000.00. |
| destination_address | string | — | Crypto rail: a 0x-prefixed address on Base to receive USDC. When set, the withdrawal goes on-chain instead of to a bank account. |
| recipient_id | string | — | Bank rail: the saved bank account to pay (wrec_...). Omit to be shown the saved accounts. |
| Name | Type | Req | Description |
|---|---|---|---|
| amountUsd | string | — | Requested amount in USD. |
| message | string | yes | Human-readable result or next step. |
| withdrawalId | string | — | Reference id of the created withdrawal request. |
No examples provided.