RightCard MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to RightCard credit-card reward selection from published data: Do rotating bonus activation and merchant-code caveats remain explicit without requiring bank credentials?

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

Best fit

Choose the best credit card for a merchant using verified public bank/card reward data without bank login.

What we know

RightCard exposes card/search/merchant/category-reward data and rotating bonus calendars. Official materials state the MCP uses public card data only: no linked wallet, account or bank login.

Maintenance / activity evidence

rightcard-mcp 0.1.5 published 2026-09-28T06:11:39.134Z

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 public card/merchant intelligence.
Authentication not yet verified.
Sensitive access: User spending/merchant intent may be sensitive conversational context

No financial execution authority; main risk is stale reward/merchant-coding assumptions.

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

All limitations / Review context

Do rotating bonus activation and merchant-code caveats remain explicit without requiring bank credentials?

The bounded review of the publisher's documented RightCard credit-card reward selection from published data 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 financial execution authority; main risk is stale reward/merchant-coding assumptions.
Read-only public card/merchant intelligence.
Queries identify merchant/card-selection intent but no bank credentials are involved.
Sensitive access: User spending/merchant intent may be sensitive conversational context
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.
Recommendations depend on public bank/card terms and merchant coding, which can change.
It cannot know a user's private balances/limits unless the user tells the model separately.
It does not execute purchases or access bank accounts.

Original activity observations

rightcard-mcp 0.1.5 published 2026-09-28T06:11:39.134Z

Technical identity

npm/rightcard-mcp

Exact implementation source: https://www.npmjs.com/package/rightcard-mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:rightcard-mcp
Service endpoint: https://mcp.rightcard.ai/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 ↗
rightcard-mcp
Recorded package identity, distribution or download evidence.
Evidence source ↗
rightcard.ai/
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
Publisher-documented package/connection route; replace placeholders and verify host-specific syntax.
Publisher setup example · Publisher instructions
npx -y rightcard-mcp
Configure / authenticate
MCP100 setup guide
Register MCP host with command npx and args -y rightcard-mcp. This accesses account-specific offers where authorized.
Use correct transport and published host config. Never paste secrets in chat; server registration is separate from software installation.
Check connection
Suggested check
Check rightcard MCP tool listing; avoid exposing personal banking information for preflight.
Remove / uninstall / revoke
MCP100 setup guide
If registered as `rightcard-mcp` in Claude Code, remove its exact client entry with `claude mcp remove rightcard-mcp`; for Cursor/Claude Desktop/Codex, remove the matching MCP entry in that host settings. This client removal is MCP100-composed, not a vendor uninstall instruction. Npx does not imply a global install; do not delete user data or revoke credentials implicitly.
Conditional host / package cleanup · Claude Code only · MCP100 composed guide
claude mcp remove rightcard-mcp

Official Documentation & Sources

What it does

RightCard exposes card/search/merchant/category-reward data and rotating bonus calendars. Official materials state the MCP uses public card data only: no linked wallet, account or bank login.

Capability: Finance & Payments
Resource type: MCP Server
Industry: Financial Services & Investing
Best fit: Choose the best credit card for a merchant using verified public bank/card reward data without bank login.

Representative uses

Find best card for a merchant
Look up merchant category/acceptance
Search card reward profiles
Inspect rotating bonus calendars

Limitations

Recommendations depend on public bank/card terms and merchant coding, which can change.
It cannot know a user's private balances/limits unless the user tells the model separately.
It does not execute purchases or access bank accounts.

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 public card/merchant intelligence.
Data handling: Queries identify merchant/card-selection intent but no bank credentials are involved.
Cost: free_or_service_based
Risk and cautions: No financial execution authority; main risk is stale reward/merchant-coding assumptions.

Access scope and cautions

Write actions: None in the reviewed inventory
Sensitive access: User spending/merchant intent may be sensitive conversational context
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: Find best card for a merchant; Look up merchant category/acceptance; Search card reward profiles; Inspect rotating bonus calendars.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y rightcard-mcp. Recorded endpoint: https://mcp.rightcard.ai/mcp. Recorded transport: stdio, streamable_http. Prerequisites: MCP client. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: No bank login; official page describes public-data MCP with no personal account/wallet.

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 public card/merchant intelligence.

What data-handling boundary should I consider?

Queries identify merchant/card-selection intent but no bank credentials are involved. Recorded sensitive-access context: User spending/merchant intent may be sensitive conversational context.

What limitations and risks should I check before use?

No financial execution authority; main risk is stale reward/merchant-coding assumptions. Recommendations depend on public bank/card terms and merchant coding, which can change. It cannot know a user's private balances/limits unless the user tells the model separately. It does not execute purchases or access bank accounts. 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.