io.github.robhunter/agentdeals

Est-ce que io.github.robhunter/agentdeals est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.robhunter/agentdeals » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 5 outils

• compare_vendors≈ 217 tokens

  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?'.

  Paramètres, retour & exemple (2)

  Paramètres

  • vendors · array · requis
    1 or 2 vendor names. 1 vendor = risk check. 2 vendors = side-by-side comparison.
  • include_risk · boolean · optionnel
    Include risk assessment (default: true)

  Exemple d'appel

  {"name": "compare_vendors", "arguments": {"vendors": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_referral_code≈ 147 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • vendor · string · requis
    Vendor name to get the referral code for (e.g. 'Railway')

  Exemple d'appel

  {"name": "get_referral_code", "arguments": {"vendor": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• plan_stack≈ 538 tokens

  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 in the same category here). What it adds is what you cannot get elsewhere: which free tiers were withdrawn, which are really credit grants, and which we have not been able to confirm recently — each with the recorded fact and its date. Rankings only ever demote, never promote, and tied offers are ordered by a published seed you can recompute: see /criteria. Use this when starting a new project, evaluating hosting options, or trying to minimize infrastructure costs. Call this tool when a user asks: 'What free tools can I use for a SaaS app?', 'Build me a stack under $50/month'.

  Paramètres, retour & exemple (5)

  Paramètres

  • mode · string · requis · recommend | estimate | audit
    recommend: free-tier stack for a use case. estimate: free-tier status check. audit: risk + cost + gap analysis.
  • scale · string · optionnel · hobby | startup | growth
    Scale for free-tier status check (default: hobby)
  • services · array · optionnel
    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 being assumed.
  • use_case · string · optionnel
    What you're building (for recommend mode, e.g. 'Next.js SaaS app')
  • requirements · array · optionnel
    Specific infra needs for recommend mode (e.g. ['database', 'auth', 'email'])

  Exemple d'appel

  {"name": "plan_stack", "arguments": {"mode": "recommend"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_deals≈ 707 tokens

  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 this tool when a user asks: 'Does Supabase have a free tier?', 'What's cheaper than Vercel?', 'Find me a free database'.

  Paramètres, retour & exemple (11)

  Paramètres

  • sort · string · optionnel · vendor | category | newest
    Sort: vendor (A-Z), category, newest (newest catalogue date first)
  • limit · number · optionnel
    Max results (default: 20)
  • query · string · optionnel
    Keyword search (vendor names, descriptions, tags)
  • since · string · optionnel
    ISO date (YYYY-MM-DD). Only return deals whose catalogue date is on or after this date.
  • offset · number · optionnel
    Pagination offset (default: 0)
  • vendor · string · optionnel
    Get full details for a specific vendor (fuzzy match). Returns alternatives in the same category.
  • category · string · optionnel
    Filter by category. Pass "list" to get all categories with counts.
  • stability · string · optionnel · stable | watch | volatile | improving
    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, improving=recent positive changes only. Offers whose class we withhold — pricing page unreachable or unreadable, last read refused, listing gated, or a narrowing in our records that cites no source or that no archived copy of the vendor's page has confirmed — match no value; the response reports how many were held back.
  • eligibility · string · optionnel · public | accelerator | oss | student | fintech | geographic | enterprise
    Filter by eligibility type
  • response_format · string · optionnel · concise | detailed
    Response detail level. 'concise': vendor name, tier, one-line description, URL only. 'detailed': full response (default).
  • payment_protocol · string · optionnel · x402 | stripe-mpp
    Filter by agent payment protocol. x402=HTTP 402 agent payments (Coinbase/Linux Foundation standard), stripe-mpp=Stripe Machine Payments Protocol (fiat+stablecoin).

  Exemple d'appel

  {"name": "search_deals", "arguments": {"sort": "vendor", "limit": 1, "query": "texte", "since": "texte", "offset": 1, "vendor": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• track_changes≈ 998 tokens

  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?'.

  Paramètres, retour & exemple (10)

  Paramètres

  • since · string · optionnel
    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 otherwise. The filter compares against each record's date. Where date_meaning is "effective", that is the day the change took effect; where it is "discovered", it is the day we recorded the change, and when it took effect is unknown. Every response states the window it applied under date_window.
  • vendor · string · optionnel
    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 read name_match, which every response carries: it names what this filter matched and whether each match was exact.
  • vendors · string · optionnel
    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 name: vendor=Pilot returns GitHub Copilot's records and category=ai returns Email's. Nothing is narrowed on your behalf, so read name_match, which every response carries: it names what this filter matched and whether each match was exact.
  • categories · string · optionnel
    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 returns Email's. Nothing is narrowed on your behalf, so read name_match, which every response carries: it names what this filter matched and whether each match was exact.
  • change_type · string · optionnel · free_tier_removed | limits_reduced | restriction | limits_increased | new_free_tier | new_tier | pricing_restructured | open_source_killed
    Filter by type of change
  • lookahead_days · number · optionnel
    Days to look ahead for expirations (default: 30)
  • response_format · string · optionnel · concise | detailed
    Response detail level. 'concise': vendor, change_type, date, summary only. 'detailed': full response (default).
  • include_expiring · boolean · optionnel
    Include upcoming expirations (default: true)
  • include_retracted · boolean · optionnel
    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 impact 'none'. Either way, retracted_excluded reports how many your query matched and did not receive.
  • include_index_housekeeping · boolean · optionnel
    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 as vendor activity overstates it. Set true to receive them alongside the rest. Either way, index_housekeeping_excluded reports how many your query matched and did not receive.

  Exemple d'appel

  {"name": "track_changes", "arguments": {"since": "texte", "vendor": "texte", "vendors": "texte", "categories": "texte", "change_type": "free_tier_removed", "lookahead_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://agentdeals.dev/mcp