io.github.aarbchen/signaltender-mcp

Est-ce que io.github.aarbchen/signaltender-mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.aarbchen/signaltender-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 15 outils

• analyze_rfp_amendment_diff≈ 660 tokens

  Diff base RFP/SOW text against subsequent SF-30 Solicitation Amendments, SLED Addenda, and official Government Q&A logs to flag altered `shall`/`must` mandates, deadline extensions, page-limit revisions, CLIN pricing changes, de-facto Q&A requirements, and invalidated proposal sections with Shipley redraft language. This is a read-only, stateless change-impact analysis call (requires X-RapidAPI-Key; `base_solicitation_text` and `amendment_or_qa_text` accept up to 100,000 characters each, and providing optional `current_proposal_outline` enables targeted auditing of which specific drafted proposal volumes/pages are invalidated). Use this tool whenever an agency issues an SF-30 amendment, addendum, or Q&A response matrix after initial RFP release; use `generate_compliance_matrix` instead when shredding an initial base RFP for the first time.

  Paramètres, retour & exemple (3)

  Paramètres

  • amendment_or_qa_text · string · requis
    Subsequent SF-30 Amendment text, state/local SLED Addendum text, or official Contracting Officer Q&A clarification matrix to diff against the base solicitation.
  • base_solicitation_text · string · requis
    Original base RFP text from Section B (CLINs), Section C/PWS (Statement of Work), Section L (Instructions/Deadlines/Page Limits), or Section M (Evaluation Criteria).
  • current_proposal_outline · string · optionnel
    Optional summary of the bidder's in-progress proposal outline, volume page allocations, or technical baseline used to pinpoint exact sections that must be rewritten.

  Exemple d'appel

  {"name": "analyze_rfp_amendment_diff", "arguments": {"amendment_or_qa_text": "texte", "base_solicitation_text": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"material_requirement_changes": [], "invalidated_proposal_sections": [], "schedule_and_page_limit_changes": {}}}

• answer_security_questionnaire≈ 790 tokens

  Draft audit-ready responses to vendor security questionnaires (SOC 2, ISO 27001, FedRAMP Moderate/High, NIST SP 800-171 Rev 2/3, CMMC 2.0, CAIQ/SIG/HECVAT) with cross-framework control citations, an estimated DoD SPRS score (-203 to 110), required evidence artifacts, and POA&M remediation items for any control gaps. This is a read-only, stateless advisory responder (requires X-RapidAPI-Key; maps each question in `questionnaire_text` against the vendor's `security_posture_summary`, while `target_framework` selects 'auto_detect' [default] or locks control citations to a specific standard and flags any unsupported controls as 'Partially Met' or 'POA&M Required' rather than fabricating compliance). Use this tool when completing customer due-diligence questionnaires, SSP control tables, or DoD SPRS self-assessments; use `scan_far_dfars_clauses` instead to audit FAR/DFARS solicitation clauses, or `generate_compliance_matrix` for general RFP Section C/L/M requirements.

  Paramètres, retour & exemple (3)

  Paramètres

  • target_framework · string · optionnel · auto_detect | soc2_iso27001 | nist_800_171_cmmc | fedramp_800_53 | caiq_sig_hecvat
    Compliance control mapping mode: 'auto_detect' (default, infers framework from questionnaire text), 'soc2_iso27001' (AICPA TSC & ISO 27001 Annex A), 'nist_800_171_cmmc' (110 CMMC 2.0 Level 2 controls + DoD SPRS score calculation), 'fedramp_800_53' (NIST SP 800-53 Rev 5), or 'caiq_sig_hecvat'.
  • questionnaire_text · string · requis
    Numbered or bulleted security questionnaire items from an enterprise SIG/CAIQ/HECVAT sheet, customer infosec assessment, or Federal RFP / NIST 800-171 SSP checklist.
  • security_posture_summary · string · requis
    Required summary of the vendor's actual security stack, cloud hosting (e.g., AWS GovCloud), active certifications (SOC 2 Type II, ISO 27001, FedRAMP), encryption (FIPS 140-3, AES-256), MFA/IAM, and SIEM logging.

  Exemple d'appel

  {"name": "answer_security_questionnaire", "arguments": {"questionnaire_text": "texte", "security_posture_summary": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"detected_framework": "texte", "question_responses": [], "poam_remediation_items": [], "estimated_dod_sprs_score": 1}}

• audit_contract_risks≈ 531 tokens

  Audit commercial and B2B legal agreements (MSAs, NDAs, SaaS terms, subcontracts) to detect high-risk clauses, compute a 0-100 overall risk score, and generate verbatim clause quotes paired with ready-to-paste fallback redline language. This operation is read-only, stateless, and non-destructive (requires X-RapidAPI-Key; `raw_text` accepts 50 to 100,000 characters, and `party_perspective` shifts redline rewrites to protect the 'vendor', 'buyer', or 'neutral' counsel). Use this tool when reviewing commercial/legal terms (indemnification, liability caps, IP ownership, termination for convenience); use `scan_far_dfars_clauses` instead for federal FAR/DFARS/CMMC regulatory flow-down audits, or `parse_b2b_contract` for basic metadata extraction.

  Paramètres, retour & exemple (2)

  Paramètres

  • raw_text · string · requis
    Full or partial legal contract text (MSA, NDA, subcontract, or SaaS agreement) to audit for commercial, IP, indemnification, and termination risks (50 to 100,000 characters).
  • party_perspective · string · optionnel · vendor | buyer | neutral
    Negotiating party perspective ('vendor' protects service provider liability/IP, 'buyer' strengthens customer remedies/SLAs, 'neutral' balances mutual terms).

  Exemple d'appel

  {"name": "audit_contract_risks", "arguments": {"raw_text": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"risk_level": "texte", "flagged_clauses": [], "overall_risk_score": 1}}

• classify_naics_psc_nigp≈ 760 tokens

  Map any company profile, product description, or Statement of Work (SOW) into ranked 6-digit NAICS codes (with official SBA Small Business Size Standards in revenue or headcount), 4-digit SIC codes, 4-character Federal PSC codes, and State NIGP/UNSPSC commodity codes. This is a read-only, stateless taxonomy classification call (requires X-RapidAPI-Key; `description_text` is required, `context_type` tunes code selection for vendor KYB profiles vs. RFP scopes, and `max_secondary_codes` [1-5, default 3] controls how many secondary NAICS/PSC alternatives are returned alongside the primary code). Use this tool whenever you need industry, procurement, or KYB taxonomy codes and SBA small-business size caps; use `search_historical_awards` instead to query past contract awards once you have a NAICS code, or `parse_b2b_contract` to extract contract dates and dollar values.

  Paramètres, retour & exemple (3)

  Paramètres

  • context_type · string · optionnel · company_or_vendor_profile | rfp_or_sow_scope | product_or_service_catalog
    Input context mode: 'company_or_vendor_profile' (default, optimizes for SAM.gov vendor registration & FinTech KYB SIC/NAICS), 'rfp_or_sow_scope' (optimizes for solicitation set-aside NAICS & Federal PSC), or 'product_or_service_catalog' (emphasizes NIGP/UNSPSC commodity codes).
  • description_text · string · requis
    Unstructured text describing a company's offerings, a B2B product catalog, or a government RFP/SOW technical scope (20 to 50,000 characters).
  • max_secondary_codes · integer · optionnel
    Maximum number of secondary/alternative NAICS, PSC, and NIGP codes to return in addition to the top-ranked primary code (integer 1 to 5; defaults to 3).

  Exemple d'appel

  {"name": "classify_naics_psc_nigp", "arguments": {"description_text": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"sic_codes": [], "primary_naics": {}, "federal_psc_codes": [], "secondary_naics_codes": [], "state_unspsc_and_nigp_codes": []}}

• extract_pricing_schedule≈ 727 tokens

  Extract multi-tier CLIN/SLIN pricing schedules, GSA/T&M labor rate cards, vendor quotes, and Bill of Materials (BOM) tables from unstructured text into normalized JSON with automated line-item math auditing. This is a read-only, stateless extraction call (requires X-RapidAPI-Key; `document_text` accepts 20 to 100,000 characters, `expected_document_type` optionally hints the table schema, and `audit_math_and_anomalies` [default true] verifies `quantity * unit_price == extended_price` and flags arithmetic discrepancies). Use this tool when parsing pricing tables, CLIN schedules, invoices, or labor rate cards; use `parse_b2b_contract` instead for general contract dates/parties/deliverables, or `search_historical_awards` to look up historical government award prices.

  Paramètres, retour & exemple (3)

  Paramètres

  • document_text · string · requis
    Raw text or copied table content from a Federal Section B CLIN schedule, T&M labor rate card, B2B vendor quote, BOM, or invoice (20 to 100,000 characters).
  • expected_document_type · string · optionnel · auto_detect | federal_section_b_clin_schedule | gsa_or_tm_labor_rate_card | b2b_vendor_quote_or_bom | commercial_invoice
    Document schema hint: 'auto_detect' (default), 'federal_section_b_clin_schedule' (parses Base/Option Year CLINs & contract types like FFP/T&M), 'gsa_or_tm_labor_rate_card' (LCAT hourly rates), 'b2b_vendor_quote_or_bom', or 'commercial_invoice'.
  • audit_math_and_anomalies · boolean · optionnel
    When true (default), cross-checks each line item (`quantity * unit_price == total_price`) and subtotal summation, returning any arithmetic mismatches in `math_discrepancies`.

  Exemple d'appel

  {"name": "extract_pricing_schedule", "arguments": {"document_text": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"line_items": [], "math_discrepancies": [], "calculated_grand_total": 1, "detected_document_type": "texte", "dominant_pricing_model": "texte"}}

• generate_ato_rmf_package≈ 1110 tokens

  Transform RFP cybersecurity clauses, system architecture descriptions, and cloud hosting baselines into a NIST SP 800-53 Rev 5 / DoDI 8510.01 RMF / FedRAMP / StateRAMP Authority to Operate (ATO & Continuous ATO) package with FIPS 199 / CNSSI 1253 security categorization, System Security Plan (SSP) control inheritance matrices, eMASS/CSAM-ready Plan of Action & Milestones (POA&M) schedules, Continuous Monitoring (ConMon) DevSecOps blueprints, and Shipley proposal narratives. This is a read-only, stateless generative authorization modeling call (requires X-RapidAPI-Key; `system_architecture_and_rfp_cyber_text` accepts 40 to 100,000 characters, `cloud_hosting_and_inherited_controls_context` accepts 20 to 80,000 characters, and `target_authorization_framework` and `target_impact_level` calibrate control baselines across DoD RMF IL2-IL6, FedRAMP, StateRAMP, and CMMC 2.0). Use this tool when building System Security Plans (SSPs), eMASS POA&M items, FIPS 199 categorizations, or cATO roadmaps for an ATO boundary; use `answer_security_questionnaire` instead to answer vendor security questionnaires and calculate a numeric DoD SPRS score (-203 to 110), or `scan_far_dfars_clauses` to audit FAR/DFARS solicitation clauses.

  Paramètres, retour & exemple (4)

  Paramètres

  • target_impact_level · string · optionnel · IL2_LOW | IL4_MODERATE_CUI | IL5_CUI_NSS | IL6_CLASSIFIED_HIGH | FEDRAMP_MODERATE | FEDRAMP_HIGH
    Target DoD Cloud Computing SRG Impact Level or FIPS 199 baseline: 'IL2_LOW', 'IL4_MODERATE_CUI', 'IL5_CUI_NSS' (default), 'IL6_CLASSIFIED_HIGH', 'FEDRAMP_MODERATE', or 'FEDRAMP_HIGH'.
  • target_authorization_framework · string · optionnel · dod_rmf_dodi_8510_01_cato | fedramp_rev5_agency_ato | stateramp_txramp_govramp | nist_800_171_cmmc_level_2
    Target authorization framework: 'dod_rmf_dodi_8510_01_cato' (default DoD RMF & Continuous ATO), 'fedramp_rev5_agency_ato' (Civilian Federal Agency ATO / FedRAMP Rev 5), 'stateramp_txramp_govramp' (State SLED StateRAMP / TX-RAMP / GovRAMP), or 'nist_800_171_cmmc_level_2' (CMMC 2.0 Level 2).
  • system_architecture_and_rfp_cyber_text · string · requis
    Raw RFP Section C/L/M cybersecurity & ATO requirements, target system architecture, data types processed (CUI, CDI, ITAR, PHI, PII, CJIS), user communities, and interconnection boundaries (40 to 100,000 characters).
  • cloud_hosting_and_inherited_controls_context · string · requis
    Cloud Service Provider (CSP) enclave (AWS GovCloud, Azure Government, GCP Assured Workloads, on-prem), platform layer (Kubernetes, Platform One BigBang, Serverless), and existing security tooling (SIEM, SOAR, ICAM, SAST/DAST).

  Exemple d'appel

  {"name": "generate_ato_rmf_package", "arguments": {"system_architecture_and_rfp_cyber_text": "texte", "cloud_hosting_and_inherited_controls_context": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"control_inheritance_summary": "texte", "authorization_boundary_summary": "texte", "continuous_ato_conmon_blueprint": {}, "emass_poam_remediation_schedule": [], "fips_199_security_categorization": {}, "ssp_control_implementation_matrix": []}}

• generate_compliance_matrix≈ 564 tokens

  Shred unstructured RFP Section C (SOW/PWS), Section L (Instructions), and Section M (Evaluation Criteria) text into a numbered `shall`/`must` Requirements Traceability Matrix, Section L-to-M cross-reference map, and annotated Proposal Outline with page allocations. This is a read-only, stateless analysis operation (requires X-RapidAPI-Key; `raw_text` accepts 50 to 100,000 characters, and `proposal_methodology` selects 'shipley' [default Volume I-IV structure], 'federal_standard' [FAR 15.3], or 'commercial_agile' outline conventions). Use this tool first when shredding a base RFP into a compliance checklist and proposal outline; use `analyze_rfp_amendment_diff` instead when comparing an SF-30 amendment against a base RFP, or `generate_rfp_response` to draft the actual prose narrative for a specific section.

  Paramètres, retour & exemple (2)

  Paramètres

  • raw_text · string · requis
    Raw RFP Section C (Statement of Work / PWS), Section L (Instructions to Offerors), and/or Section M (Evaluation Factors) text (50 to 100,000 characters).
  • proposal_methodology · string · optionnel · shipley | federal_standard | commercial_agile
    Proposal structuring methodology: 'shipley' (default evaluator-first Volume I-IV outline with win themes), 'federal_standard' (strict FAR Part 15 Section L/M mapping), or 'commercial_agile' (B2B solution deliverable sprints).

  Exemple d'appel

  {"name": "generate_compliance_matrix", "arguments": {"raw_text": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"proposal_outline": [], "requirements_matrix": []}}

• generate_cpars_past_performance≈ 734 tokens

  Transform unstructured project histories, prior contract summaries, and CPARS excerpts into Shipley Section L/M Past Performance Volume III citations with predicted DoD Source Selection Relevance ('Very Relevant' to 'Not Relevant') and Performance Confidence ratings, Scope/Magnitude/Complexity matrices, FAR 42.1503 5-Factor CPARS narratives, and Context-Challenge-Action-Result (CCAR) blocks. This is a read-only, stateless generative evaluation call where relevance/confidence ratings are model-inferred against Section M criteria (requires X-RapidAPI-Key; `rfp_section_l_m_requirements` and `project_history_text` accept up to 100,000 characters, and optional `bidder_role_and_context` calibrates Prime vs. Subcontractor/JV attribution and page budgets). Use this tool when building Volume III Past Performance contract citations and CPARS questionnaires; use `generate_rfp_response` instead for Volume I Technical Approach prose, or `match_key_personnel` for individual staff resumes.

  Paramètres, retour & exemple (3)

  Paramètres

  • project_history_text · string · requis
    Unstructured prior contract summaries, internal project delivery notes, or official CPARS evaluation excerpts (contract numbers, agencies, dollar values, FTEs, KPIs, and technical accomplishments).
  • bidder_role_and_context · string · optionnel
    Optional pursuit context specifying Prime vs. Subcontractor citation mix, Joint Venture / SBA Mentor-Protege structure (13 CFR 125.8), or Volume III page-limit constraints.
  • rfp_section_l_m_requirements · string · requis
    Target RFP Section L (Volume III Past Performance instructions, recency window, minimum annual/total dollar value, max citations), Section M (relevance evaluation criteria), and Section C/PWS core task areas.

  Exemple d'appel

  {"name": "generate_cpars_past_performance", "arguments": {"project_history_text": "texte", "rfp_section_l_m_requirements": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"tailored_citations": [], "gap_mitigation_strategies": [], "overall_confidence_assessment": "texte"}}

• generate_igce_price_to_win≈ 990 tokens

  Model an Independent Government Cost Estimate (IGCE), compounded Indirect Wrap-Rate breakdown (Fringe, Overhead, G&A, and Fee/Profit), GSA CALC+ aligned LCAT rate card, multi-year Section B CLIN pricing schedule, 4-scenario Price-to-Win (PTW) sensitivity matrix, and Shipley Volume IV Basis of Estimate (BOE) narrative from RFP Section B/SOW text. This is a read-only, stateless financial modeling and estimation call (requires X-RapidAPI-Key; `rfp_section_b_and_sow_text` accepts 30 to 120,000 characters, optional `historical_benchmark_and_incumbent_context` and `bidder_indirect_wrap_assumptions` anchor indirect multipliers and incumbent baselines, and `evaluation_methodology` calibrates FAR 15.101-1 Best-Value Tradeoff vs. LPTA or FAR 15.404-1(d) Cost Realism). Use this tool when building forward-looking Volume IV Price/Cost models, wrap-rate build-ups, and Price-to-Win targets; use `search_historical_awards` instead to query past FPDS/SAM award records, or `extract_pricing_schedule` to parse an existing vendor quote or invoice table.

  Paramètres, retour & exemple (4)

  Paramètres

  • evaluation_methodology · string · optionnel · BEST_VALUE_TRADEOFF | LPTA_LOWEST_PRICE_TECHNICALLY_ACCEPTABLE | HIGHEST_TECHNICALLY_RATED_FAIR_REASONABLE_PRICE | COST_REALISM_CPFF
    Source selection evaluation methodology: 'BEST_VALUE_TRADEOFF' (FAR 15.101-1), 'LPTA_LOWEST_PRICE_TECHNICALLY_ACCEPTABLE' (FAR 15.101-2), 'HIGHEST_TECHNICALLY_RATED_FAIR_REASONABLE_PRICE', or 'COST_REALISM_CPFF' (FAR 15.404-1(d)).
  • rfp_section_b_and_sow_text · string · requis
    Raw RFP Section B (Supplies or Services and Prices/Costs), PWS/SOW level-of-effort & LCAT staffing requirements, contract type (FFP, T&M, Labor-Hour, CPFF), Period of Performance (Base + Option Years), and Place of Performance (Contractor-site vs. Government-site).
  • bidder_indirect_wrap_assumptions · string · optionnel
    Optional bidder indirect rate assumptions (Fringe %, Overhead %, G&A %, Target Fee/Profit %, annual productive hours per FTE such as 1,880 or 1,920, and annual Option Year escalation %).
  • historical_benchmark_and_incumbent_context · string · optionnel
    Optional incumbent contract value, FPDS/USAspending historical award benchmarks, GSA MAS SIN 54151S CALC+ ceiling rates, or known agency budget ceilings to anchor the IGCE and Price-to-Win model.

  Exemple d'appel

  {"name": "generate_igce_price_to_win", "arguments": {"rfp_section_b_and_sow_text": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ptw_sensitivity_scenarios": [], "recommended_price_to_win_usd": 1, "lcat_rate_card_and_fte_buildup": [], "wrap_rate_calculator_breakdown": {}, "cost_realism_and_price_reasonableness_posture": "texte", "independent_government_cost_estimate_igce_usd": 1}}

• generate_oral_presentation_prep≈ 1081 tokens

  Generate a FAR 15.102 & Shipley Phase-II Oral Presentation slide-by-slide blueprint, Key Personnel speaker-attributed talking points, a minute-by-minute Live Technical Demonstration / Scenario Challenge runbook with zero-downtime failover contingencies, an adversarial SSEB 'Murder Board' Q&A coaching matrix, and evaluator caucus takeaways from RFP Section L/M oral instructions. This is a read-only, stateless generative preparation call (requires X-RapidAPI-Key; `rfp_oral_instructions_and_sow_text` accepts 30 to 120,000 characters, `proposed_solution_and_key_personnel` maps slides strictly to eligible Key Personnel speakers, optional `known_incumbent_and_risk_areas` sharpens Murder-Board trap questions, and `presentation_format_mode` selects 'COMBINED_ORALS_TECH_DEMO_AND_QA' [default], 'EXECUTIVE_SLIDE_BRIEFING_AND_QA', 'LIVE_TECHNICAL_SCENARIO_CHALLENGE', or 'KEY_PERSONNEL_INTERVIEW_AND_CAUCUS'). Use this tool when preparing for Phase-II advisory down-select oral presentations, live technical demonstrations, or SSEB Q&A caucuses; use `generate_rfp_response` instead for written Volume I Technical Approach prose, or `match_key_personnel` for written Volume II resumes and Letters of Commitment.

  Paramètres, retour & exemple (4)

  Paramètres

  • presentation_format_mode · string · optionnel · COMBINED_ORALS_TECH_DEMO_AND_QA | EXECUTIVE_SLIDE_BRIEFING_AND_QA | LIVE_TECHNICAL_SCENARIO_CHALLENGE | KEY_PERSONNEL_INTERVIEW_AND_CAUCUS
    Oral presentation format mode: 'COMBINED_ORALS_TECH_DEMO_AND_QA' (default, slide deck + live technical demo + Q&A), 'EXECUTIVE_SLIDE_BRIEFING_AND_QA' (Shipley slide deck + Q&A), 'LIVE_TECHNICAL_SCENARIO_CHALLENGE' (on-the-spot engineering problem/coding challenge), or 'KEY_PERSONNEL_INTERVIEW_AND_CAUCUS' (structured SSEB oral interview).
  • known_incumbent_and_risk_areas · string · optionnel
    Optional competitive context, incumbent vulnerabilities, transition risks, or technical gaps where the Source Selection Evaluation Board (SSEB) is likely to probe during Murder-Board Q&A.
  • rfp_oral_instructions_and_sow_text · string · requis
    Raw RFP Section L Oral Presentation / Live Tech-Demo rules (time limits, slide limits, speaker eligibility restrictions under FAR 15.102, live scenario prompts), Section M evaluation criteria, and PWS/SOW technical scope (30 to 120,000 characters).
  • proposed_solution_and_key_personnel · string · requis
    Proposed technical/management solution architecture, key discriminators, and named Key Personnel speakers (roles, clearances, domain expertise, and past performance proof points) who will present.

  Exemple d'appel

  {"name": "generate_oral_presentation_prep", "arguments": {"rfp_oral_instructions_and_sow_text": "texte", "proposed_solution_and_key_personnel": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"slide_deck_blueprint": [], "live_tech_demo_runbook": [], "murder_board_qa_matrix": [], "evaluator_caucus_takeaways": [], "predicted_oral_confidence_rating": "texte"}}

• generate_rfp_response≈ 808 tokens

  Draft an evaluator-ready Shipley proposal narrative (complete with Win Themes, Feature-Benefit-Proof blocks, and Risk Mitigations) AND a list of strategic Contracting Officer Clarification Q&A questions from an RFP section and company capabilities. This is a read-only, stateless composite generation call that always returns both the drafted narrative and the clarification questions in a single JSON payload (requires X-RapidAPI-Key; `target_section_type` selects the proposal section format, and `tone_and_methodology` customizes the writing style). Use this tool when writing Technical Approach, Executive Summary, or Management Plan prose; use `generate_compliance_matrix` instead to build a requirement checklist/outline first, or `generate_cpars_past_performance` for structured Volume III CPARS contract citations.

  Paramètres, retour & exemple (4)

  Paramètres

  • rfp_section_text · string · requis
    Verbatim RFP Section C/PWS technical requirements, Section L instructions, or Section M evaluation criteria that the drafted proposal section must satisfy.
  • target_section_type · string · optionnel · technical_approach | executive_summary | management_and_staffing_plan | past_performance_narrative
    Target proposal section structure: 'technical_approach' (default, solution architecture & requirement execution), 'executive_summary' (vision & discriminators), 'management_and_staffing_plan' (governance, transition & QA), or 'past_performance_narrative' (prose summary).
  • tone_and_methodology · string · optionnel
    Editorial voice and methodology instruction applied to the prose draft (defaults to 'Shipley Proposal Methodology (Active Voice, Evaluator-First, Feature-Benefit-Proof)').
  • company_context_and_capabilities · string · requis
    Bidder's technical architecture, past performance metrics, SLAs, certifications, and competitive discriminators to weave into the narrative.

  Exemple d'appel

  {"name": "generate_rfp_response", "arguments": {"rfp_section_text": "texte", "company_context_and_capabilities": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"section_title": "texte", "drafted_narrative_markdown": "texte", "win_themes_and_discriminators": [], "strategic_clarification_questions": []}}

• generate_teaming_strategy≈ 828 tokens

  Generate a legally compliant GovCon Teaming Strategy, a 13 CFR 125.6 & FAR 52.219-14 (Limitations on Subcontracting / 50% Rule) Prime/Sub workshare split, Ostensible Subcontractor risk audit, partner archetypes, FAR Subpart 9.6 Teaming Agreement clauses, and a BD outreach email. This is a read-only, stateless compliance and strategy generator (requires X-RapidAPI-Key; `set_aside_type` enforces SBA workshare ceilings for 'sdvosb' [default], '8a', 'wosb_edwosb', 'hubzone', 'small_business', or 'full_and_open', while `bidder_role` tailors outputs for 'prime_seeking_subs' [default], 'sub_seeking_prime', or 'joint_venture_mentor_protege'). Use this tool when structuring Prime/Sub workshare splits or recruiting teaming partners to fill capability gaps; use `match_capability_statement` instead for an initial single-vendor Bid/No-Bid Pwin score.

  Paramètres, retour & exemple (4)

  Paramètres

  • rfp_text · string · requis
    Raw RFP scope, PWS task areas, contract ceiling, security clearance requirements, and FAR 52.219-14 / set-aside instructions.
  • bidder_role · string · optionnel · prime_seeking_subs | sub_seeking_prime | joint_venture_mentor_protege
    Bidder's teaming posture: 'prime_seeking_subs' (default, allocates >=50% to Prime and defines sub gap archetypes), 'sub_seeking_prime' (positions bidder for 20-49% specialty workshare), or 'joint_venture_mentor_protege' (13 CFR 125.8 JV compliance).
  • set_aside_type · string · optionnel · full_and_open | small_business | sdvosb | 8a | wosb_edwosb | hubzone
    Solicitation set-aside designation ('sdvosb' [default], '8a', 'wosb_edwosb', 'hubzone', 'small_business', or 'full_and_open') used to enforce 13 CFR 125.6 similarly situated entity and 50% self-performance rules.
  • bidder_capabilities · string · requis
    Bidder's socioeconomic status, self-performed technical domains, clearance level, and past performance strengths.

  Exemple d'appel

  {"name": "generate_teaming_strategy", "arguments": {"rfp_text": "texte", "bidder_capabilities": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"workshare_allocation": {}, "partner_outreach_email": "texte", "teaming_agreement_clauses": [], "ostensible_subcontractor_risk": "texte", "recommended_partner_archetypes": []}}

• get_live_solicitations≈ 588 tokens

  Retrieve currently open, AI-vetted Federal (SAM.gov) and State/Local SLED (VA, TX, CA, FL, MD, IL, PA, OH, GA, DemandStar) IT, Cloud, and Cybersecurity solicitations from SignalTender's 11-portal procurement database. This is a read-only, non-destructive live database query (requires X-RapidAPI-Key; all four filter parameters are optional and combinable, returning up to `limit` [default 10, max 50] active solicitations whose closing dates have not passed). Use this tool when discovering active open RFPs to bid on right now; use `search_historical_awards` instead for past awarded contracts and incumbent pricing, or `match_capability_statement` once you have selected an RFP to score Bid/No-Bid Pwin.

  Paramètres, retour & exemple (4)

  Paramètres

  • limit · integer · optionnel
    Maximum number of open solicitations to return per request (integer between 1 and 50; defaults to 10).
  • state · string · optionnel · federal | virginia | texas | california | florida | maryland | illinois | pennsylvania
    Optional jurisdiction portal filter ('federal' for SAM.gov, 'virginia', 'texas', 'california', 'florida', 'maryland', 'illinois', 'pennsylvania', 'ohio', 'georgia', or 'municipal' for DemandStar).
  • keyword · string · optionnel
    Optional case-insensitive substring keyword matched against solicitation title and issuing buyer agency.
  • category · string · optionnel · cybersecurity | cloud-infrastructure | software-development | network-telecom
    Optional technology vertical filter ('cybersecurity', 'cloud-infrastructure', 'software-development', or 'network-telecom').

  Exemple d'appel

  {"name": "get_live_solicitations", "arguments": {"limit": 1, "state": "federal", "keyword": "texte", "category": "cybersecurity"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"count": 1, "solicitations": []}}

• match_capability_statement≈ 705 tokens

  Evaluate an RFP scope against a vendor's Capability Statement and past performance to compute a 0-100 Probability of Win (Pwin) score, a Gate-1 Bid/No-Bid recommendation, a technical/socioeconomic gap analysis, and a tailored executive pitch. This is a read-only, stateless capture scoring call (requires X-RapidAPI-Key; both `rfp_text` and `company_capability_statement` are required, while `target_pursuit_role` weights eligibility rules for 'prime_contractor', 'subcontractor', or 'either_prime_or_sub' [default]). Use this tool at Gate-1 capture qualification to decide whether to bid an opportunity; use `generate_teaming_strategy` instead if you already decided to bid and need a 13 CFR 125.6 (50% Rule) Prime/Sub workshare plan, or `match_key_personnel` to evaluate individual candidate resumes.

  Paramètres, retour & exemple (3)

  Paramètres

  • rfp_text · string · requis
    Target solicitation scope, mandatory technical qualifications, NAICS/set-aside designation, clearance requirements, and Section M evaluation criteria.
  • target_pursuit_role · string · optionnel · prime_contractor | subcontractor | either_prime_or_sub
    Intended pursuit role: 'prime_contractor' enforces strict set-aside and past-performance minimums, 'subcontractor' scores niche workshare fit, and 'either_prime_or_sub' (default) recommends the highest-Pwin path.
  • company_capability_statement · string · requis
    Vendor capability statement including core competencies, socioeconomic certifications (8(a), SDVOSB, WOSB, HUBZone), facility clearances, and past performance summary.

  Exemple d'appel

  {"name": "match_capability_statement", "arguments": {"rfp_text": "texte", "company_capability_statement": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"pwin_score": 1, "capability_gaps": [], "bid_recommendation": "texte", "tailored_executive_pitch": "texte", "strengths_and_discriminators": []}}

• match_key_personnel≈ 766 tokens

  Evaluate a candidate's resume against RFP Section L/M Key Personnel and GSA MAS / OASIS+ / Alliant 3 Labor Category (LCAT) requirements (years of experience, education, security clearance, DoD 8570/8140 certifications), rewrite relevant roles into a Shipley Key Personnel bio, and generate a ready-to-sign Letter of Commitment (LOC). This is a read-only, stateless qualification audit and resume formatter that does not store candidate PII (requires X-RapidAPI-Key; `allow_education_experience_substitution` [default true] applies standard federal GSA/OPM equivalency rules such as Bachelor's + 4 years = Master's when scoring eligibility). Use this tool when qualifying and formatting individual Key Personnel resumes for a proposal; use `match_capability_statement` instead to score overall company-level Bid/No-Bid Pwin, or `generate_cpars_past_performance` for company-level contract citations.

  Paramètres, retour & exemple (3)

  Paramètres

  • candidate_resume_text · string · requis
    Candidate's unstructured resume or CV including education degrees, active security clearances, professional certifications (CISSP, PMP, AWS, etc.), and chronological work history.
  • lcat_or_rfp_requirements · string · requis
    Raw RFP Section L/M Key Personnel instructions, GSA MAS / GWAC Labor Category (LCAT) minimum qualifications, required security clearance, and mandatory DoD 8570/8140 certifications.
  • allow_education_experience_substitution · boolean · optionnel
    When true (default), applies standard federal GSA/OPM degree-for-experience substitution rules (e.g., Bachelor's + 4 additional years of specialized experience satisfies a Master's requirement) unless the RFP text explicitly prohibits substitutions.

  Exemple d'appel

  {"name": "match_key_personnel", "arguments": {"candidate_resume_text": "texte", "lcat_or_rfp_requirements": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"compliance_verdict": "texte", "qualification_score": 1, "letter_of_commitment_loc": "texte", "requirement_audit_matrix": [], "tailored_shipley_resume_markdown": "texte"}}

• parse_b2b_contract≈ 689 tokens

  Extract structured contract metadata (contracting parties, effective and termination dates, total contract value, payment terms, key deliverables, security clearances, and governing law) from unstructured B2B contracts, Statements of Work (SOWs), or RFPs into normalized JSON. This is a read-only, stateless, non-destructive extraction call (requires X-RapidAPI-Key; accepts 50 to 100,000 characters in `raw_text`, and `document_type_hint` optionally biases extraction rules toward federal RFP, MSA, SOW, or NDA conventions). Use this tool when you need general commercial or header metadata from a contract; use `extract_pricing_schedule` instead for line-by-line CLIN/rate-card tables, `audit_contract_risks` for toxic clause redlining, or `generate_compliance_matrix` for Section C/L/M requirement shredding.

  Paramètres, retour & exemple (2)

  Paramètres

  • raw_text · string · requis
    Raw unstructured text from a B2B contract, Master Services Agreement (MSA), Statement of Work (SOW), or Request for Proposal (RFP) between 50 and 100,000 characters.
  • document_type_hint · string · optionnel · RFP | MSA | SOW | NDA | SUBCONTRACT | AUTO
    Optional document classification hint ('RFP', 'MSA', 'SOW', 'NDA', 'SUBCONTRACT', or 'AUTO') used to prioritize federal solicitation fields vs. commercial agreement terms.

  Exemple d'appel

  {"name": "parse_b2b_contract", "arguments": {"raw_text": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"parties": [], "deliverables": [], "document_type": "texte", "governing_law": "texte", "payment_terms": "texte", "effective_date": "texte", "total_contract_value": 1, "termination_or_due_date": "texte"}}

• scan_far_dfars_clauses≈ 583 tokens

  Scan solicitation Section I or subcontract flow-down text to identify every FAR (`52.2xx`) and DFARS (`252.2xx`) clause, flag mandatory subcontractor flow-downs, and score CMMC 2.0, NIST SP 800-171, and FedRAMP compliance burden. This is a read-only, stateless regulatory audit (requires X-RapidAPI-Key; `raw_text` accepts 30 to 100,000 characters, and `contractor_role` adjusts risk severity and flow-down obligations for a 'prime_contractor' [default], 'subcontractor', or 'commercial_item_vendor' under FAR Part 12). Use this tool specifically for federal acquisition regulation (FAR/DFARS/CMMC) clause compliance; use `audit_contract_risks` instead for commercial MSA/NDA legal redlining, or `answer_security_questionnaire` to draft control-by-control NIST 800-171 / SOC 2 questionnaire responses.

  Paramètres, retour & exemple (2)

  Paramètres

  • raw_text · string · requis
    Solicitation Section I, contract clause list, or subcontract agreement text containing FAR (`52.2xx`) or DFARS (`252.2xx`) citations (30 to 100,000 characters).
  • contractor_role · string · optionnel · prime_contractor | subcontractor | commercial_item_vendor
    Bidder's contracting tier: 'prime_contractor' (evaluates full agency compliance and outbound flow-down duties), 'subcontractor' (flags over-broad prime flow-downs), or 'commercial_item_vendor' (filters against FAR 52.212-5 commercial item exemptions).

  Exemple d'appel

  {"name": "scan_far_dfars_clauses", "arguments": {"raw_text": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"detected_clauses": [], "compliance_burden_score": 1, "cybersecurity_posture_summary": "texte"}}

• search_historical_awards≈ 508 tokens

  Query historical federal contract awards, incumbent prime contractors, award ceilings, and labor/CLIN pricing benchmarks filtered by keyword, agency, or 6-digit NAICS code. This is a read-only, deterministic database query (requires X-RapidAPI-Key; `keywords` is required and narrows scope descriptions, while optional `agency` and 6-digit `naics_code` filters intersect results and return up to 25 matching awards per call). Use this tool when researching past award prices, incumbent vendors, or Price-to-Win (PTW) benchmarks; use `get_live_solicitations` instead to find currently open RFPs available for bidding, or `classify_naics_psc_nigp` if you need to discover the right NAICS code first.

  Paramètres, retour & exemple (3)

  Paramètres

  • agency · string · optionnel
    Optional issuing federal or state agency name substring filter (e.g., 'Department of Defense', 'Veterans Affairs').
  • keywords · string · requis
    Required technical or domain search keywords matched against award descriptions and CLIN titles (e.g., 'zero trust', 'cloud migration', 'SIEM').
  • naics_code · string · optionnel
    Optional exact 6-digit North American Industry Classification System (NAICS) code filter (e.g., '541512' for Computer Systems Design).

  Exemple d'appel

  {"name": "search_historical_awards", "arguments": {"keywords": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"awards": [], "total_matches": 1}}

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://b2b-contract-parser-api.onrender.com/mcp