Open Solid
REMOTE · OPENSOLID.AI
Banking for AI agents: wallet, US bank account, prepaid cards, and Venmo, PayPal, and bank payouts.
Available components
Last scanned (3 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: this server exposes a tool marked destructive (pay) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability55
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 433 tokens (~43/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 24 Oct 26 59
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 5 Nov 2026 · Probed https://opensolid.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.opensolid.ai | CN=YR1,O=Let's Encrypt,C=US | 16 Oct 2026 | 14 Jan 2027 | RSA 2048 | SHA256-RSA | 63f1849f5d1f1ea3c418d5941824d6e0ff1 |
| SANs: *.opensolid.ai, opensolid.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of opensolid.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| opensolid.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://opensolid.ai/mcp | Verified | 200 | |
| http (plaintext) | http://opensolid.ai/mcp | HTTPS enforced | 308 | https://opensolid.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
announce_connection Announce connection ~32
Tell your human you connected. Call first.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | yes | – |
| message | string | – | – |
No output schema declared.
No examples provided.
get_activity Get activity ~15
Recent payments, deposits and connections.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_banking Get bank account ~16
US bank account numbers and transfers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_cards Get cards ~37
Reloadable cards, or one card's details with card_id.
| Name | Type | Req | Description |
|---|---|---|---|
| card_id | string | – | – |
| card_type | string | – | – |
No output schema declared.
No examples provided.
get_kyc_status Get identity status ~20
Whether the account owner has verified their identity.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_pricing Get pricing ~17
Fees and limits for every payment type.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_spend_limit Get spend limit ~21
The per-payment limit your human set. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_wallet Get wallet ~21
Wallet addresses (Solana, Base) and USDC balances.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_recipients List payout recipients ~31
Saved payout recipients for a rail: venmo, paypal or bank.
| Name | Type | Req | Description |
|---|---|---|---|
| rail | string | – | – |
No output schema declared.
No examples provided.
pay Make a payment ~199
PAID. Make a payment from the wallet: type is usa_card, gift_card, venmo, paypal, bank, debit, or x402 (call any x402-priced API: give url, max_usd and optionally method and body; returns the API's response). Enforces the spend limit on the fee-inclusive total. Always include a one-sentence note.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | – |
| body | object | – | – |
| country | string | – | – |
| currency | string | – | – |
| destination_id | string | – | – |
| first_name | string | – | – |
| idempotency_key | string | – | – |
| laso_server_id | string | – | – |
| last_name | string | – | – |
| max_usd | number | – | – |
| method | string | – | – |
| note | string | yes | – |
| recipient_id | string | – | – |
| type | string | yes | – |
| url | string | – | – |
No output schema declared.
No examples provided.
How do I install the Open Solid MCP server?
Open Solid is a hosted endpoint at https://opensolid.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · opensolid.ai
claude mcp add --transport http ai-opensolid-opensolid 'https://opensolid.ai/mcp'
What is the Open Solid MCP server?
Open Solid is an MCP server listed in the public MCP registry as ai.opensolid/opensolid. Banking for AI agents: wallet, US bank account, prepaid cards, and Venmo, PayPal, and bank payouts. This page covers its hosted endpoint (https://opensolid.ai/mcp).
Is the Open Solid MCP server safe to use?
Open Solid scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Open Solid MCP server expose?
Open Solid exposes 10 tools: announce_connection, get_wallet, get_spend_limit, get_activity, get_pricing, and 5 more. Their descriptions and schemas cost roughly 409 tokens of context every time the server is loaded.
Does the Open Solid MCP server require authentication?
No. We connected to Open Solid without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Open Solid MCP server still maintained?
Open Solid is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.