BentCrypto Machine Payments
REMOTE · API.BENTCRYPTO.COM · SCANNED SEP 20
Paid token risk and security intelligence for AI agents over MCP with x402 payments.
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 → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 208 tokens (~104/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the BentCrypto Machine Payments MCP server?
BentCrypto Machine Payments is a hosted endpoint at https://api.bentcrypto.com/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 · api.bentcrypto.com
claude mcp add --transport http ghstaking-bentcrypto-machine-payments 'https://api.bentcrypto.com/mcp'
{
"mcpServers": {
"ghstaking-bentcrypto-machine-payments": {
"url": "https://api.bentcrypto.com/mcp"
}
}
} {
"servers": {
"ghstaking-bentcrypto-machine-payments": {
"type": "http",
"url": "https://api.bentcrypto.com/mcp"
}
}
} [mcp_servers.ghstaking-bentcrypto-machine-payments] url = "https://api.bentcrypto.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ghstaking-bentcrypto-machine-payments": {
"type": "remote",
"url": "https://api.bentcrypto.com/mcp",
"enabled": true
}
}
} openclaw mcp add ghstaking-bentcrypto-machine-payments --url 'https://api.bentcrypto.com/mcp' --transport streamable-http
mcp_servers:
ghstaking-bentcrypto-machine-payments:
url: "https://api.bentcrypto.com/mcp" {
"McpServers": {
"ghstaking-bentcrypto-machine-payments": {
"Transport": "http",
"Url": "https://api.bentcrypto.com/mcp"
}
}
} assistant mcp add ghstaking-bentcrypto-machine-payments -t streamable-http -u 'https://api.bentcrypto.com/mcp'
{
"mcpServers": {
"ghstaking-bentcrypto-machine-payments": {
"type": "http",
"url": "https://api.bentcrypto.com/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.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 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.
- 5 Sept 26 +3
- Schema quality: 57 → 104 ▼ functional
- Tool coverage: 50% → 100% ▲ functional
- Tool “token_risk” now declares an output schema ▲ functional
- Tool “token_security” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Schema quality: good → excellent functional
- “token_risk” reworded the description of “address” cosmetic
- “token_risk” reworded the description of “chain” cosmetic
- “token_security” reworded the description of “address” cosmetic
- “token_security” reworded the description of “chain” cosmetic
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 20 Sept 2026 · Probed https://api.bentcrypto.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.bentcrypto.com | CN=YE1,O=Let's Encrypt,C=US | 7 Aug 2026 | 5 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 6399d8b28362e7d5cc9fe3aec51701de208 |
| SANs: api.bentcrypto.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.bentcrypto.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| bentcrypto.com. | 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=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.bentcrypto.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.bentcrypto.com/mcp | HTTPS enforced | 301 | https://api.bentcrypto.com/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 →
token_risk BentCrypto Token Risk ~118
Paid pre-trade token risk analysis. Supports Solana and Base. The HTTP transport returns an x402 challenge before private analysis executes.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Token mint or contract address on the selected chain. Example Solana: So11111111111111111111111111111111111111112. Example Base: 0x4200000000000000000000000000000000000006. |
| chain | string | – | Blockchain to analyze. Supported values are Solana and Base; defaults to Solana when omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Token mint or contract address analyzed. |
| chain | string | – | Blockchain analyzed. |
| confidence | object | – | Evidence confidence and coverage information. |
| metadata | object | – | Analysis provenance and execution metadata. |
| risk | object | – | Risk assessment generated from available on-chain and market evidence. |
| success | boolean | – | Whether the analysis request completed successfully. |
No examples provided.
token_security BentCrypto Token Security ~90
Paid Solana token-control analysis covering mint/freeze authority and Token-2022 control risks. The HTTP transport returns an x402 challenge before private analysis executes.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Solana token mint address to inspect. Example: So11111111111111111111111111111111111111112. |
| chain | string | – | Blockchain to analyze. Token Security currently supports Solana only. |
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Solana token mint address analyzed. |
| chain | string | – | Blockchain analyzed; Token Security currently supports Solana only. |
| confidence | object | – | Evidence confidence and coverage information. |
| freeze_authority | – | – | Freeze-authority finding when exposed by the analysis engine. |
| metadata | object | – | Analysis provenance and execution metadata. |
| mint_authority | – | – | Mint-authority finding when exposed by the analysis engine. |
| risk | object | – | Security and token-control risk findings. |
| success | boolean | – | Whether the security analysis completed successfully. |
| token_2022 | object | – | Token-2022 extension and control findings when applicable. |
No examples provided.
What is the BentCrypto Machine Payments MCP server?
BentCrypto Machine Payments is an MCP server listed in the public MCP registry as io.github.ghstaking/bentcrypto-machine-payments. Paid token risk and security intelligence for AI agents over MCP with x402 payments. This page covers its hosted endpoint (https://api.bentcrypto.com/mcp).
Is the BentCrypto Machine Payments MCP server safe to use?
BentCrypto Machine Payments scores 84 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 BentCrypto Machine Payments MCP server expose?
BentCrypto Machine Payments exposes 2 tools: token_risk, token_security. Their descriptions and schemas cost roughly 208 tokens of context every time the server is loaded.
Does the BentCrypto Machine Payments MCP server require authentication?
No. We connected to BentCrypto Machine Payments without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the BentCrypto Machine Payments MCP server still maintained?
BentCrypto Machine Payments is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.