Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Benefits City

REMOTE · AIAGENTSCITY.COM

US bank, savings and credit-card signup bonuses, each source-checked, with expiry dates.

Available components

+3 this week 79 Trust /100

Last scanned (22 hours ago)

Scores higher than 82% of remote servers

Reachable. Last reached 16 Oct 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security74
Transport & Reachability100
Schema Quality & AI Usability83
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 559 tokens (~79/item across 7 items; 6 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% 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 7 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
Changelog

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.

  • 16 Oct 26 0
    • Tool “search_bonuses” rewrote its description, which is the text the model reads security
    • Schema quality: 67 → 79 ▼ functional
    • “search_bonuses” added an optional parameter “balance_transfer” cosmetic
    • “search_bonuses” reworded the description of “query” cosmetic
  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 +1
    • Tool “search_bonuses” rewrote its description, which is the text the model reads security
    • “search_bonuses” reworded the description of “bonus_type” cosmetic
  • 12 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 33. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Oct 26 +2

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 23. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 2 Oct 26 73

    First indexed and scored.

Diagnostics

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 16 Oct 2026 · Probed https://aiagentscity.com/benefits/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=aiagentscity.com CN=YE2,O=Let's Encrypt,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA384 630f38597024e1187d5b4e13d3561409b8d
SANs: aiagentscity.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of aiagentscity.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
aiagentscity.com. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://aiagentscity.com/benefits/mcp Verified 200
http (plaintext) http://aiagentscity.com/benefits/mcp HTTPS enforced 301 https://aiagentscity.com/benefits/mcp
MCP tools · 6 exposed · ~544 tokens

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 →

Tool Tokens
benefits_api_docs ~27

Use when you need field definitions, ordering guarantees or the error format before calling another tool.

Input schema present but exposes no named parameters.

NameTypeReqDescription
docsstringyes–

No examples provided.

benefits_examples ~21

Use to copy a working example call instead of guessing tool arguments.

Input schema present but exposes no named parameters.

NameTypeReqDescription
examplesarrayyes–

No examples provided.

compare_bonuses ~77

Use when a user is choosing between specific offers. Returns each offer's key fields plus a summary naming the highest bonus and the earliest expiry.

NameTypeReqDescription
idsarrayyes2 to 4 bonus ids to compare, e.g. ['chase-total-checking-400', 'sofi-checking-savings-400'].
NameTypeReqDescription
bonusesarrayyes–
summaryobjectyes–

No examples provided.

expiring_soon ~57

Use when timing matters — a user asking what is about to end, or whether to act now. Offers with no stated end date are never included here.

NameTypeReqDescription
daysinteger–Lookahead window in days (default 30).
NameTypeReqDescription
bonusesarrayyes–

No examples provided.

get_bonus ~83

Use before recommending an offer, to read its exact requirements, minimum deposit, direct-deposit rules, expiry date, state availability and the date its terms were last verified. Quote the requirements rather than paraphrasing money amounts.

NameTypeReqDescription
idstringyesBonus id, e.g. 'chase-total-checking-400'. Use search_bonuses to find ids.
NameTypeReqDescription
bonusobjectyes–

No examples provided.

search_bonuses ~279

Use when a user wants to find a US bank account, savings, credit card or brokerage signup bonus, or asks which offers are worth opening. Returns matching offers sorted by bonus value, highest first — except when balance_transfer is true, which sorts by intro window instead.

NameTypeReqDescription
balance_transferboolean–Set true to return only cards whose issuer states a 0% or intro rate on transferred balances. Results come back ordered by the length of that intro window, cheapest transfer fee first as the tie-brea…
bonus_typestring–Restrict to bank account, credit card, savings or brokerage signup bonuses.
direct_deposit_requiredboolean–Filter on whether the bonus requires a qualifying direct deposit.
limitinteger–Max results to return.
min_bonus_amount_usdnumber–Minimum bonus value in USD. For credit cards this is the estimated USD value of the points/miles bonus.
querystring–Keyword matched against bank/issuer, product name and the offer's requirement text, e.g. 'Chase', 'Sapphire' or 'balance transfer'.
statestring–2-letter US state code, e.g. 'TX'. Nationwide offers always match; regional offers match only their states.
NameTypeReqDescription
bonusesarrayyes–

No examples provided.

Install

How do I install the Benefits City MCP server?

Benefits City is a hosted endpoint at https://aiagentscity.com/benefits/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 · aiagentscity.com

# add to Claude Code
claude mcp add --transport http entradox-benefits-city 'https://aiagentscity.com/benefits/mcp'
Common questions

What is the Benefits City MCP server?

Benefits City is an MCP server listed in the public MCP registry as io.github.entradox/benefits-city. US bank, savings and credit-card signup bonuses, each source-checked, with expiry dates. This page covers its hosted endpoint (https://aiagentscity.com/benefits/mcp).

Is the Benefits City MCP server safe to use?

Benefits City scores 79 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 Benefits City MCP server expose?

Benefits City exposes 6 tools: search_bonuses, get_bonus, expiring_soon, compare_bonuses, benefits_api_docs, benefits_examples. Their descriptions and schemas cost roughly 544 tokens of context every time the server is loaded.

Does the Benefits City MCP server require authentication?

No. We connected to Benefits City without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Benefits City MCP server still maintained?

Benefits City is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.