accueil / serveurs / Dev & Code / io.github.Kabrawala/pubsec-sales-mcp
io.github.Kabrawala/pubsec-sales-mcp
serveur MCP (Model Context Protocol) · pubsec-sales 0.1.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 io.github.Kabrawala/pubsec-sales-mcp est sûr ?
Au dernier audit MCP Hub, le serveur MCP « io.github.Kabrawala/pubsec-sales-mcp » 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
- agency_spend_profile≈ 236 tokens
Use this to answer "what does this agency actually buy, and from whom?" before a first call: total contract obligations, 3-year trend, top 10 vendors, and top 10 NAICS categories for the latest fiscal year with published data. Good queries name one agency, e.g. agency="HHS". Figures come from a daily snapshot of USAspending (latest published fiscal year plus a 3-year trend); the fiscal year and freshness are stated in the response. Federal only. Read the coverage caveats — in-progress fiscal years are partial, and intel-agency spend is never published.
Paramètres, retour & exemple (1)
Paramètresagency· string · requis
Federal agency name, acronym, or code — e.g. "HHS", "Department of Veterans Affairs", "075".
Exemple d'appel{"name": "agency_spend_profile", "arguments": {"agency": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - find_expiring_contracts≈ 355 tokens
Use this when prospecting or prepping a federal account and you want sales triggers: contracts at an agency that end soon, with the incumbent vendor, dollar values, and contracting office. Expiring contracts mean upcoming recompetes — the best time to displace an incumbent. Good queries name one agency and optionally a NAICS code, e.g. agency="DHS", naics_code="541512", window_days=90. Federal only (no state/local). Every response includes data-freshness and coverage caveats — read them; no data ≠ no spend.
Paramètres, retour & exemple (4)
Paramètreslimit· integer · optionnel
Max contracts to return (top by obligated amount). Default 15.agency· string · requis
Federal agency name, acronym, or code — e.g. "DHS", "Department of Defense", "070". Federal only; SLED is out of scope.naics_code· string · optionnel
Optional NAICS code to narrow by category, e.g. "541512" (computer systems design).window_days· integer · optionnel
How far ahead to look for contract end dates, in days from today. Default 90, max 365.
Exemple d'appel{"name": "find_expiring_contracts", "arguments": {"agency": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - generate_discovery_questions≈ 368 tokens
Use this when prepping a meeting with a federal agency: it returns discovery questions tuned to public-sector selling (fiscal-year timing, contract vehicles, FedRAMP/ATO, incumbents), grounded in the agency's live spending data where possible — each data-backed question cites the number that motivated it with a source URL. Good queries name the agency, what you sell, and the meeting type, e.g. agency="DHS", product_category="zero-trust network security", meeting_context="first_call". Add naics_code to surface expiring-contract questions.
Paramètres, retour & exemple (4)
Paramètresagency· string · requis
Federal agency the meeting is with — name, acronym, or code, e.g. "DHS".naics_code· string · optionnel
Optional NAICS code for your category — adds questions about specific expiring contracts.meeting_context· string · optionnel · first_call | technical_deep_dive | procurement_discussion
What kind of meeting you are prepping for.product_category· string · requis
What you sell, in plain words — e.g. "data analytics platform", "zero-trust network security".
Exemple d'appel{"name": "generate_discovery_questions", "arguments": {"agency": "texte", "product_category": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - incumbent_lookup≈ 292 tokens
Use this to answer "who am I displacing and when?": a vendor name (plus optional agency scope) returns their current and recent awards with values and end dates, flagging awards that end within 12 months as displacement windows. Good queries use the vendor's registered name or a distinctive fragment, e.g. vendor="Booz Allen", agency="DHS". Federal only. Zero results ≠ no presence — check the caveats for name-matching tips.
Paramètres, retour & exemple (3)
Paramètreslimit· integer · optionnel
Max awards to return (largest first). Default 15.agency· string · optionnel
Optional federal agency to scope the lookup, e.g. "DHS". Omit to search government-wide.vendor· string · requis
Vendor/incumbent name as registered in federal awards, e.g. "Booz Allen Hamilton", "CACI". FPDS matches it as a phrase — shorter fragments match more.
Exemple d'appel{"name": "incumbent_lookup", "arguments": {"vendor": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - qualify_opportunity≈ 642 tokens
Use this to pressure-test a federal deal: pass what you know per MEDDPICC dimension (leave unknowns empty) and get back an evidence-scored scorecard adapted for public sector — budget authority instead of generic economic buyer, procurement vehicle as the paper process — with gap-closing questions and public-record evidence pulled automatically (name the incumbent_vendor and their real awards/end dates at the agency get attached). Scores measure evidence specificity, not truth; the response says what verified evidence looks like for each dimension.
Paramètres, retour & exemple (5)
Paramètresagency· string · requis
Federal agency the deal is at — name, acronym, or code, e.g. "DHS".deal_facts· object · optionnel
What you know so far, one field per MEDDPICC dimension. Omit entirely (or leave fields empty) for pure-discovery scoring — gaps are the output.incumbent_vendor· string · optionnel
Competitor/incumbent vendor name if known — their real awards at this agency get pulled as evidence.product_category· string · requis
What you are selling, e.g. "SIEM platform".estimated_value_usd· number · optionnel
Rough deal size in USD, if known.
Exemple d'appel{"name": "qualify_opportunity", "arguments": {"agency": "texte", "product_category": "texte"}}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é ».