accueil / serveurs / Recherche & Web / cc.rockpool.ai-deals/ai-deals-sentinel
cc.rockpool.ai-deals/ai-deals-sentinel
serveur MCP (Model Context Protocol) · ai-deals-sentinel 1.0.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que cc.rockpool.ai-deals/ai-deals-sentinel est sûr ?
Au dernier audit MCP Hub, le serveur MCP « cc.rockpool.ai-deals/ai-deals-sentinel » 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 3 outils
- check_api_health≈ 769 tokens
The last measured liveness of free public data APIs (weather, geo, finance, knowledge, news, public-health and developer APIs): HTTP status and latency from one read-only GET per API, with the generated_at of that measurement. status SLOW means the API timed out at 10s and answered a 45s re-probe (works, not fast); DOWN means no answer within 45s; SKIP means the API needs a key and was not called. counts.measured excludes SKIP rows, so it is the health denominator, not counts.total. It does not measure AI model provider APIs.
Paramètres, retour & exemple (1)
Paramètresapi· string · optionnel
Substring match on API name; omit for all
Exemple d'appel{"name": "check_api_health", "arguments": {"api": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"feed": {}, "counts": {}, "results": [], "feed_build": {}, "server_build": {}, "denominator_note": "texte"}} - find_free_inference≈ 829 tokens
Lists free tiers, signup credits, trial credits and discounts on AI APIs: inference, GPU, search, embeddings, vector databases, speech and vision, eval and observability, and compute sandboxes. Filters by capability and by provider or offer name. Each row gives limits, offer_status, access (what the first call needs: api-key, credit-card, oauth, web-form, phone-verification, account or none, or null), source_url, verified_at and verified_days_ago. A row with access credit-card needs a payment card to get that offer; a null access is not a sign of card-free access. Rows state what the provider advertised on verified_at, not today.
Paramètres, retour & exemple (3)
Paramètresprovider· string · optionnel
Substring match on provider or offer namecapability· string · optionnel
Filter by category, e.g. inference, gpu, search, embeddings, vector-db, speech-vision, eval-observability, compute-sandboxagent_usable_only· boolean · optionnel
Only offers an agent can consume via API once a human clears the signup. Defaults to true.
Exemple d'appel{"name": "find_free_inference", "arguments": {"provider": "texte", "capability": "texte", "agent_usable_only": true}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"count": 1, "offers": [], "feed_build": {}, "server_build": {}, "freshness_note": "texte", "feed_assembled_at": "texte"}} - get_offer≈ 877 tokens
Full record for one provider's offer, matched by provider or offer name: limits, caveats, deal_type, offer_status, access (what the first call needs, such as api-key or credit-card; or null, which is not a sign that no card is needed), expires_at, source_url, verified_at and verified_days_ago. offer_status is available, retired, unverified, or none (checked, and no free API path was found). Covers questions such as whether a provider has a free API, whether its free tier is still on as of verified_at, what its free limits are, and whether a card is needed. On no match it returns the nearest candidates rather than an empty result.
Paramètres, retour & exemple (1)
Paramètresprovider· string · requis
Provider or offer name
Exemple d'appel{"name": "get_offer", "arguments": {"provider": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "offers": [], "matched": true, "feed_build": {}, "suggestions": [], "server_build": {}, "freshness_note": "texte", "feed_assembled_at": "texte", "untrusted_third_party_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é ».