Paid Base Token Tools
REMOTE · PAID-MCP-OPPORTUNITY-LAB--TAYLORBOUCHER1.REPLIT.APP
Base token facts and ERC-20 allowance checks. Per-call USDC on Base; x402 wallet required.
Available components
Last scanned (2 hours ago)
Scores higher than 87% of remote servers
Reachable. Last reached 5 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 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 Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 449 tokens (~74/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 43% of tool parameters carry a description.Partial
- Structured output schemas are declared (17% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 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 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.
- 30 Oct 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.
- 28 Oct 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.
- 26 Oct 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.
- 23 Oct 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.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
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://paid-mcp-opportunity-lab--taylorboucher1.replit.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=replit.app | CN=WR3,O=Google Trust Services,C=US | 28 Oct 2026 | 26 Jan 2027 | RSA 2048 | SHA256-RSA | ec3ae2dfc6c55a2e109aff41a0e4b4c3 |
| SANs: replit.app, *.replit.app | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of paid-mcp-opportunity-lab--taylorboucher1.replit.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| replit.app. | 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; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://paid-mcp-opportunity-lab--taylorboucher1.replit.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://paid-mcp-opportunity-lab--taylorboucher1.replit.app/api/mcp | HTTPS enforced | 301 | https://paid-mcp-opportunity-lab--taylorboucher1.replit.app:443/api/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 →
base_token_allowance ~94
Read an ERC-20 allowance on Base at a pinned block before an AI proposes spending. Returns exact units, decimals and provenance. Does not approve or transfer tokens. Version 253064e6ce6110d8. Requires 0.01 native USDC per call on Base; shared paid pilot limits apply.
| Name | Type | Req | Description |
|---|---|---|---|
| ownerAddress | – | yes | – |
| spenderAddress | – | yes | – |
| tokenAddress | string | yes | – |
No output schema declared.
No examples provided.
base_token_facts ~72
Read a Base ERC-20 fact packet at one pinned block: metadata, exact supply, bytecode hash and EIP-1967 implementation slot. Requires 0.01 native USDC on Base; no financial advice.
| Name | Type | Req | Description |
|---|---|---|---|
| tokenAddress | string | yes | ERC-20 contract address on Base mainnet |
No output schema declared.
No examples provided.
base_uniswap_v3_lp_accounting_audit ~176
Read official Base Uniswap V3 NFT and pool state at one canonical block hash. Reconcile exact token inventory and fee-growth checkpoints against optional reported raw amounts. Return signed discrepancies, reproducible inputs and uint128 accounting semantics. Recorded tokensOwed may include withdrawn principal, not only fees. Read-only; no USD valuation, trading, custody or profitability claim. Version 234e52e42b53afb8. Requires 0.01 native USDC per call on Base; shared paid pilot limits apply.
| Name | Type | Req | Description |
|---|---|---|---|
| blockNumber | string | – | Optional historical Base block number. Omit to use the provider's safe block. |
| positionId | string | yes | Uniswap V3 NFT position ID on Base; not an Aerodrome or V4 position. |
| reported | object | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| accruedSinceCheckpointFee0Raw | string | yes | – |
| accruedSinceCheckpointFee1Raw | string | yes | – |
| block | object | yes | – |
| comparisonStatus | string | yes | – |
| comparisons | array | yes | – |
| contractFeeIncrement0Raw | string | yes | – |
| contractFeeIncrement1Raw | string | yes | – |
| evidenceStatus | string | yes | – |
| factoryAddress | string | yes | – |
| feeEvidence | object | yes | – |
| inventory0Raw | string | yes | – |
| inventory1Raw | string | yes | – |
| mathRevision | string | yes | – |
| network | string | yes | – |
| owedAfterCheckpoint0Raw | string | yes | – |
| owedAfterCheckpoint1Raw | string | yes | – |
| ownerAddress | string | yes | – |
| poolAddress | string | yes | – |
| position | object | yes | – |
| positionId | string | yes | – |
| positionManagerAddress | string | yes | – |
| recordedTokensOwed0Raw | string | yes | – |
| recordedTokensOwed1Raw | string | yes | – |
| sources | array | yes | – |
| token0 | object | yes | – |
| token1 | object | yes | – |
| tool | string | yes | – |
| uint128WrappingObserved | boolean | yes | – |
| warnings | array | yes | – |
No examples provided.
get_runtime_tools ~39
List mounted tool versions, per-call USDC prices and input schemas. Free. Releases share the receiving wallet and pilot limits, not a universal price.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_tool_status ~32
Read the available tool's Base USDC price, receiver and setup status. Free; configuration does not prove settlement.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
preview_base_usdc ~36
Free fixed sample of native USDC's on-chain facts on Base. No other token input accepted; does not make a payment.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Paid Base Token Tools MCP server?
Paid Base Token Tools is a hosted endpoint at https://paid-mcp-opportunity-lab--taylorboucher1.replit.app/api/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 · paid-mcp-opportunity-lab--taylorboucher1.replit.app
claude mcp add --transport http app-replit-paid-mcp-opportunity-lab-taylorbouche 'https://paid-mcp-opportunity-lab--taylorboucher1.replit.app/api/mcp'
What is the Paid Base Token Tools MCP server?
Paid Base Token Tools is an MCP server listed in the public MCP registry as app.replit.paid-mcp-opportunity-lab--taylorboucher1/base-to…. Base token facts and ERC-20 allowance checks. Per-call USDC on Base; x402 wallet required. This page covers its hosted endpoint (https://paid-mcp-opportunity-lab--taylorboucher1.replit.app/api/mcp).
Is the Paid Base Token Tools MCP server safe to use?
Paid Base Token Tools scores 83 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 Paid Base Token Tools MCP server expose?
Paid Base Token Tools exposes 6 tools: get_tool_status, preview_base_usdc, base_token_facts, get_runtime_tools, base_token_allowance, base_uniswap_v3_lp_accounting_audit. Their descriptions and schemas cost roughly 449 tokens of context every time the server is loaded.
Does the Paid Base Token Tools MCP server require authentication?
No. We connected to Paid Base Token Tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Paid Base Token Tools MCP server still maintained?
Paid Base Token Tools 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.