Home / MCP registry index / io.github.aarbchen/signaltender-mcp
SignalTender B2B, GovCon & LegalTech MCP Server
io.github.aarbchen/signaltender-mcp in the official MCP registry.
Endpoint https://b2b-contract-parser-api.onrender.com/mcp. Source: github.com/aarbchen/signaltender-scraper.
The registry describes it as: B2B, GovCon & LegalTech MCP server for live RFPs, contract parsing, compliance & proposal tools.
We read its 20 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
parse_b2b_contract audit_contract_risks search_historical_awards get_live_solicitations generate_compliance_matrix scan_far_dfars_clauses match_capability_statement classify_naics_psc_nigp generate_rfp_response extract_pricing_schedule generate_teaming_strategy answer_security_questionnaire match_key_personnel analyze_rfp_amendment_diff generate_cpars_past_performance generate_igce_price_to_win generate_oral_presentation_prep generate_ato_rmf_package analyze_debriefing_bid_protest generate_gsa_mas_offer
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-aarbchen-signaltender-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.