Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Agentdeals is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
MCP server aggregating developer infrastructure deals, free tiers, and startup programs
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http agentdeals-mcp https://agentdeals.dev/mcp
# 2 — ask your agent for something these tools do
# search_deals, plan_stack, compare_vendors and 2 more
Agentdeals costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http agentdeals-mcp https://agentdeals.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Find free tiers, startup credits, and developer deals for cloud infrastructure, databases, hosting, CI/CD, monitoring, auth, AI services, and more. Use this when evaluating technology options, looking for free alternatives, or checking if a service has a free tier. Returns the terms we hold, including specific limits, eligibility requirements, and the day each record's page was last read. Call thi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Keyword search (vendor names, descriptions, tags) |
| category | string | no | Filter by category. Pass "list" to get all categories with counts. |
| vendor | string | no | Get full details for a specific vendor (fuzzy match). Returns alternatives in the same category. |
| eligibility | string | no | Filter by eligibility type |
| sort | string | no | Sort: vendor (A-Z), category, newest (newest catalogue date first) |
| stability | string | no | Filter by the stability class we publish for the offer. stable=no negative changes on a pricing page we could read, watch=one negative change, volatile=free tier removed or multiple negative changes, |
| payment_protocol | string | no | Filter by agent payment protocol. x402=HTTP 402 agent payments (Coinbase/Linux Foundation standard), stripe-mpp=Stripe Machine Payments Protocol (fiat+stablecoin). |
| since | string | no | ISO date (YYYY-MM-DD). Only return deals whose catalogue date is on or after this date. |
| limit | number | no | Max results (default: 20) |
| offset | number | no | Pagination offset (default: 0) |
| response_format | string | no | Response detail level. 'concise': vendor name, tier, one-line description, URL only. 'detailed': full response (default). |
Plan a technology stack with cost-optimized infrastructure choices. In recommend mode this returns, for each role, the set of offers whose terms we can stand behind today — deliberately not a single pick, because under every signal we record dozens of them tie. It does NOT model technical fit between a product and a role; you must apply that yourself (a vector store and a relational database sit i
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mode | string | yes | recommend: free-tier stack for a use case. estimate: free-tier status check. audit: risk + cost + gap analysis. |
| use_case | string | no | What you're building (for recommend mode, e.g. 'Next.js SaaS app') |
| services | array | no | Current vendor names (for estimate/audit mode, e.g. ['Vercel', 'Supabase']). An audit analyses only names it matched exactly; anything else comes back as status not_found with suggestions rather than |
| scale | string | no | Scale for free-tier status check (default: hobby) |
| requirements | array | no | Specific infra needs for recommend mode (e.g. ['database', 'auth', 'email']) |
Compare developer tools and services side by side — free tier limits, pricing tiers, and recent pricing changes. Use this when choosing between similar services (e.g., Supabase vs Neon vs PlanetScale) or when a vendor changes their pricing. Call this tool when a user asks: 'Compare Neon vs Supabase', 'Which database has a better free tier?'.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| vendors | array | yes | 1 or 2 vendor names. 1 vendor = risk check. 2 vendors = side-by-side comparison. |
| include_risk | boolean | no | Include risk assessment (default: true) |
Track recent pricing changes across developer tools — which free tiers were removed, which got limits cut, and which improved. Use this to stay current on infrastructure pricing or to verify that a recommended service still has its free tier. Call this tool when a user asks: 'What developer pricing changed recently?', 'Are any free tiers being removed?'.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since | string | no | ISO date (YYYY-MM-DD). Default: 30 days ago, and only when no other filter is passed — a request carrying type, vendor, vendors, categories or category searches the whole change log unless since says |
| change_type | string | no | Filter by type of change |
| vendor | string | no | Filter to one vendor. Matched by case-insensitive substring, not by exact name: vendor=Pilot returns GitHub Copilot's records and category=ai returns Email's. Nothing is narrowed on your behalf, so re |
| vendors | string | no | Comma-separated vendor names to filter (e.g. 'Vercel,Supabase'). When provided with categories, returns personalized results with advisory section. Matched by case-insensitive substring, not by exact |
| categories | string | no | Comma-separated category names to filter (e.g. 'Database,Cloud Hosting'). Matched by case-insensitive substring, not by exact name: vendor=Pilot returns GitHub Copilot's records and category=ai return |
| include_expiring | boolean | no | Include upcoming expirations (default: true) |
| include_retracted | boolean | no | Records we have withdrawn as our own error (standing 'retracted') are left out unless you ask for them. Set true to receive them alongside the rest; they arrive carrying standing 'retracted' and impac |
| include_index_housekeeping | boolean | no | Records of our own index housekeeping (reports 'our_index') are left out unless you ask for them. They say we stopped listing an offer of ours, not that the vendor changed anything, so counting them a |
| lookahead_days | number | no | Days to look ahead for expirations (default: 30) |
| response_format | string | no | Response detail level. 'concise': vendor, change_type, date, summary only. 'detailed': full response (default). |
Look up the referral link we hold for a vendor, with the reader benefit and every restriction attached to it. We hold codes for a handful of vendors and earn a commission on them; /disclosure lists all of them.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| vendor | string | yes | Vendor name to get the referral code for (e.g. 'Railway') |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Agentdeals or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
The scanner has read version 0.2.0 of this listing, but not the release on the shelf, so neither a grade nor a report is shown for it here. Nothing on this tab is ever borrowed from another release or another listing.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.3.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Agentdeals can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.