BentCrypto Machine Payments
REMOTE · API.BENTCRYPTO.COM
Paid token risk and security intelligence for AI agents over MCP with x402 payments.
Available components
Last scanned (13 hours ago)
Scores higher than 96% of remote servers
Unreachable for 1 day in a row. Last reached 4 Nov 2026.
Category Crypto and Web3
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 5 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 20 Oct 26 +65
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 19 Oct 26 −65
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 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
- 25 Sept 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
- 5 Sept 26 0
- 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
- 4 Sept 26 0
- HSTS header: fail → pass ▲ security
- 30 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
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://api.bentcrypto.com/mcp
TLS unreached
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 Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
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 | Unreachable | ||
| http (plaintext) | http://api.bentcrypto.com/mcp | HTTPS enforced |
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.
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'
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 88 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?
Its publisher declares no required credentials for BentCrypto Machine Payments. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the BentCrypto Machine Payments MCP server still maintained?
BentCrypto Machine Payments is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.