TensorFeed x402 Base Reader — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Read-only Base settlement and federation receipt verification: Do on-chain receipt checks remain distinct from transaction execution and custody tools?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Independent read-only verification of x402 USDC settlements on Base without holding a wallet key.

What we know

Read-only verifier MCP that complements payment/transact servers. It checks Base-mainnet x402 settlement data and can parse publisher x402 manifests so agents can audit whether a payment actually settled on-chain.

Maintenance / activity evidence

@tensorfeed/x402-base-mcp 0.2.1 published 2026-05-28T03:45:42.093Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Read-only chain/manifest inspection.
Authentication not yet verified.
Sensitive access: Payment receipt identifiers and wallet addresses are public-chain data but may be privacy-sensitive

No asset movement authority; main risk is misinterpreting incomplete/incorrect receipt identifiers.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do on-chain receipt checks remain distinct from transaction execution and custody tools?

The bounded review of the publisher's documented Read-only Base settlement and federation receipt verification and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

No asset movement authority; main risk is misinterpreting incomplete/incorrect receipt identifiers.
Read-only chain/manifest inspection.
Public blockchain and publisher manifest data only; no wallet secret required.
Sensitive access: Payment receipt identifiers and wallet addresses are public-chain data but may be privacy-sensitive
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
It verifies settlement; it does not sign or send payments.
On-chain confirmation and publisher manifests are separate trust surfaces.
Exact helper set may evolve with x402/AFTA spec.
Keep this separate from Coinbase/Base transact-side MCP: this package verifies; it does not pay.

Original activity observations

@tensorfeed/x402-base-mcp 0.2.1 published 2026-05-28T03:45:42.093Z

Technical identity

npm/@tensorfeed/x402-base-mcp

Exact implementation source: https://www.npmjs.com/package/@tensorfeed/x402-base-mcp ↗
Reviewed resource type: MCP Server
Repository identity: RipperMercs/tensorfeed-x402-base-mcp
Package identity: npm:@tensorfeed/x402-base-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry metadata ↗
@tensorfeed/x402-base-mcp
Recorded package identity, distribution or download evidence.
Evidence source ↗
tensorfeed.ai/mcp
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
tensorfeed.ai/x402
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
tensorfeed.ai/verify
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Read threat model; distinguish verify tooling from financial transfers; x402 may involve payment credentials.
publisher documented install or connect · Publisher instructions
npm install -g @tensorfeed/x402-base-mcp
publisher documented step or launch · Publisher instructions
claude mcp add tensorfeed-x402-base -- npx -y @tensorfeed/x402-base-mcp
Configure / authenticate
MCP100 setup guide
Read-only verification-side x402 Base chain MCP: no wallet secret or transaction signing needed. Do not instruct a private key for this package.
Check connection
Suggested check
User-side suggested check (not executed): inspect registered tools/connection and perform publisher-supported read-only status/list operations. Do not send, purchase, publish, delete, sign, trade or alter data as a smoke test.
Remove / uninstall / revoke
MCP100 setup guide
Generic client guidance (not publisher-specific uninstall): unregister MCP entry in the chosen client. If installed globally, remove the npm package separately. Revoke provider access separately through account controls, where supported. This does not erase local data or revoke funds/credentials automatically.
Unregister the named MCP entry from the actual host separately from removing a global npm install; no claim that either revokes remote credentials.
Remove local stored keys/tokens and revoke or rotate corresponding provider authorization using documented provider account controls if available; exact procedure not verified for this package. Wallet private keys cannot be revoked.

Official Documentation & Sources

What it does

Read-only verifier MCP that complements payment/transact servers. It checks Base-mainnet x402 settlement data and can parse publisher x402 manifests so agents can audit whether a payment actually settled on-chain.

Capability: Finance & Payments
Resource type: MCP Server
Industry: Financial Services & Investing
Best fit: Independent read-only verification of x402 USDC settlements on Base without holding a wallet key.

Representative uses

Verify x402 settlement receipt on Base
Parse/check x402 publisher manifest
Cross-check pay-side MCP receipts independently
Use AFTA verification/federation helpers

Limitations

It verifies settlement; it does not sign or send payments.
On-chain confirmation and publisher manifests are separate trust surfaces.
Exact helper set may evolve with x402/AFTA spec.
Keep this separate from Coinbase/Base transact-side MCP: this package verifies; it does not pay.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Read-only chain/manifest inspection.
Data handling: Public blockchain and publisher manifest data only; no wallet secret required.
Cost: free_or_service_dependent
Risk and cautions: No asset movement authority; main risk is misinterpreting incomplete/incorrect receipt identifiers.

Access scope and cautions

Write actions: None in the reviewed inventory
Sensitive access: Payment receipt identifiers and wallet addresses are public-chain data but may be privacy-sensitive
Risk level: low

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Verify x402 settlement receipt on Base; Parse/check x402 publisher manifest; Cross-check pay-side MCP receipts independently; Use AFTA verification/federation helpers.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @tensorfeed/x402-base-mcp. Recorded transport: stdio. Prerequisites: Node/npm; network access to Base RPC/provider used by implementation. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: No private key required; designed as read-only chain verification.

Can it modify data or perform write operations?

The reviewed inventory lists no write actions. An empty inventory alone does not establish read-only authority. Recorded permission boundary: Read-only chain/manifest inspection.

What data-handling boundary should I consider?

Public blockchain and publisher manifest data only; no wallet secret required. Recorded sensitive-access context: Payment receipt identifiers and wallet addresses are public-chain data but may be privacy-sensitive.

What limitations and risks should I check before use?

No asset movement authority; main risk is misinterpreting incomplete/incorrect receipt identifiers. It verifies settlement; it does not sign or send payments. On-chain confirmation and publisher manifests are separate trust surfaces. Exact helper set may evolve with x402/AFTA spec. Keep this separate from Coinbase/Base transact-side MCP: this package verifies; it does not pay. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.