AgentUtility Matchpoint — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor identity continuity, MCP tool inventory, permissions and adoption.

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

Best fit

Deterministic entity matching and address/email/phone normalization through paid MCP

What we know

Deterministic entity matching and address/email/phone normalization through paid MCP. Published by the owner of npm package @agentutility/mcp-matchpoint. MCP server for the @agentutility matchpoint cluster — pay-per-call x402 tools, no API keys, USDC….

Maintenance / activity evidence

375 npm downloads, 2026-09-09 to 2026-10-08

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

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Each x402 tool call signs a USDC transfer with X402_PRIVATE_KEY; contact matching data may travel to paid remote endpoints. Reported action classes: USDC payment authorizations on tool calls. Complete write authority is not verified.
X402_PRIVATE_KEY; funded Base USDC wallet
Sensitive access: Service account information and data accessible by supplied credentials

Each x402 tool call signs a USDC transfer with X402_PRIVATE_KEY; contact matching data may travel to paid remote endpoints.
Public listing suitability does not imply safe installation or entitlement to access third-party accounts.

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

Popularity

· 375 package downloads / 30 days

Downloads observed Oct 10, 2026.

Exact npm package @agentutility/mcp-matchpoint; provider interval 2026-09-09–2026-10-08 (inclusive); observed 2026-10-10T04:43:53Z.

All limitations / Review context

Has @agentutility/mcp-matchpoint changed publishing identity, permissions, install requirements, or risk exposure?

Published package documentation reviewed; public listing with prominently disclosed risks: Each x402 tool call signs a USDC transfer with X402_PRIVATE_KEY; contact matching data may travel to paid remote endpoints.

Each x402 tool call signs a USDC transfer with X402_PRIVATE_KEY; contact matching data may travel to paid remote endpoints.
Public listing suitability does not imply safe installation or entitlement to access third-party accounts.
X402_PRIVATE_KEY; funded Base USDC wallet
Reviewed write actions: USDC payment authorizations on tool calls
Sensitive access: Service account information and data accessible by supplied credentials
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Respect upstream entitlements, version constraints and least-privilege setup.
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes.
Public exact-package npm downloads observed for recent 30-day window.

Original activity observations

375 npm downloads, 2026-09-09 to 2026-10-08

Technical identity

npm/@agentutility/mcp-matchpoint

Exact implementation source: https://www.npmjs.com/package/@agentutility/mcp-matchpoint ↗
Reviewed resource type: MCP Server
Package identity: npm:@agentutility/mcp-matchpoint

Evidence & Sources

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

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

Registry source ↗
registry.modelcontextprotocol.io/v0/servers
Source material retained for this review.
Package registry ↗
@agentutility/mcp-matchpoint
Recorded package identity, distribution or download evidence.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Financial risk: package may sign and pay for calls or buy tokens. Never use production wallet/private key to test. Obtain explicit spending approval.
A private key is not an API key; do not expose it in project files, screenshots, logs, or chat transcripts.
Chargeable by default for tool invocation: per-call USDC/x402 pricing. Tool listing or MCP registration is not a free-use guarantee.
Literal command/entry path confirmed against official README; does not validate runtime or host compatibility.
Prior reviewed safety note: Do not treat starting the MCP process as consent to transact.
Prior reviewed safety note: Do not invoke any tool merely to confirm connectivity: publisher prices its tools per call in USDC.
Prior reviewed safety note: Do not supply or fund X402_PRIVATE_KEY for initial registration.
Prior reviewed safety note: Do not delete user data or assume this cancels upstream authorizations.
Client removal, software uninstall, persistent-data deletion and credential revocation are separate actions.

Install / connect
Publisher instructions
Publisher-documented install or connect path; prerequisites and any extra host configuration remain required.
publisher install or stdio launch · Publisher instructions
npx -y @agentutility/mcp-matchpoint
Configure / authenticate
MCP100 setup guide
Register local stdio MCP JSON with command npx and args ["-y","@agentutility/mcp-matchpoint"], env X402_PRIVATE_KEY. Publisher requires funded Base USDC wallet for paid x402 calls; DO NOT substitute an API key or include private key in public config.
Check connection
Suggested check
Confirm MCP registration and tool discovery only. Calling tools can charge USDC; do not call a paid tool for verification.
Remove / uninstall / revoke
MCP100 setup guide
If registered in Claude Code under the name `agentutility-matchpoint`, remove the client entry with `claude mcp remove agentutility-matchpoint`. For other MCP hosts remove the matching server/connector in that host’s MCP settings. Remove a globally installed software package separately if applicable; this does not delete data or revoke a service credential.
Client removal, software uninstall, persistent-data deletion and credential revocation are separate actions.
Separate credential guidance (provider revocation is not verified): Publisher uses X402_PRIVATE_KEY for x402 USDC payments. Removing this variable or the MCP registration prevents new calls from this host but does not revoke the wallet private key. If exposed, rotate by creating a new wallet and handling any funds with wallet-provider guidance; no invented vendor revoke CLI.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove agentutility-matchpoint

Official Documentation & Sources

https://www.npmjs.com/package/@agentutility/mcp-matchpoint ↗

What it does

Deterministic entity matching and address/email/phone normalization through paid MCP. Published by the owner of npm package @agentutility/mcp-matchpoint. MCP server for the @agentutility matchpoint cluster — pay-per-call x402 tools, no API keys, USDC….

Capability: Data & Databases
Resource type: MCP Server
Best fit: Deterministic entity matching and address/email/phone normalization through paid MCP

Representative uses

Deterministic entity matching and address/email/phone normalization through paid MCP

Limitations

Each x402 tool call signs a USDC transfer with X402_PRIVATE_KEY; contact matching data may travel to paid remote endpoints.
Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes.
Public exact-package npm downloads observed for recent 30-day window.

Reviewed access

Access & risk

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

Authentication: X402_PRIVATE_KEY; funded Base USDC wallet
Permissions: Each x402 tool call signs a USDC transfer with X402_PRIVATE_KEY; contact matching data may travel to paid remote endpoints.
Data handling: Each x402 tool call signs a USDC transfer with X402_PRIVATE_KEY; contact matching data may travel to paid remote endpoints.
Cost: USDC x402 pay-per-call
Risk and cautions: Each x402 tool call signs a USDC transfer with X402_PRIVATE_KEY; contact matching data may travel to paid remote endpoints.

Access scope and cautions

Write actions: Not verified USDC payment authorizations on tool calls
Sensitive access: Service account information and data accessible by supplied credentials
Risk level: high
Security notes: Each x402 tool call signs a USDC transfer with X402_PRIVATE_KEY; contact matching data may travel to paid remote endpoints. Public listing suitability does not imply safe installation or entitlement to access third-party accounts.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T04:43:53Z. Watchlist tracking is not a recommendation or a security certification.

What setup and authentication are documented?

A complete connection procedure is not verified. Recorded transport: stdio. Client notes: Do not infer shell entrypoint or automated credential setup if a command is not explicitly verified. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: X402_PRIVATE_KEY; funded Base USDC wallet

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: USDC payment authorizations on tool calls. Recorded permission context: Each x402 tool call signs a USDC transfer with X402_PRIVATE_KEY; contact matching data may travel to paid remote endpoints.

What data-handling boundary should I consider?

Each x402 tool call signs a USDC transfer with X402_PRIVATE_KEY; contact matching data may travel to paid remote endpoints. Recorded sensitive-access context: Service account information and data accessible by supplied credentials.

What limitations and risks should I check before use?

Each x402 tool call signs a USDC transfer with X402_PRIVATE_KEY; contact matching data may travel to paid remote endpoints. Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes. Public exact-package npm downloads observed for recent 30-day window. Public listing suitability does not imply safe installation or entitlement to access third-party accounts. Respect upstream entitlements, version constraints and least-privilege setup.