Requirements Desk
REMOTE · SERVICES.FOREVENZA.COM
Company, sanctions, SEC and federal award lookups, document conversion, and requirement capture.
Available components
Last scanned (4 hours ago)
Scores higher than 44% of remote servers
Reachable. Last reached 5 Nov 2026.
Deprecated
This server is marked deprecated in the MCP registry.
The registry records this reason: Replaced by separate listings per business under com.forevenza.services.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability56
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 630 tokens (~78/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage72
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 15% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 +7
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: Requirements Desk → Services security
- Tool “company_financial_facts” rewrote its description, which is the text the model reads security
- Tool “entity_lookup” rewrote its description, which is the text the model reads security
- Tool “extract_web_page” rewrote its description, which is the text the model reads security
- Tool “federal_contract_awards” rewrote its description, which is the text the model reads security
- Tool “list_propositions” rewrote its description, which is the text the model reads security
- Tool “screen_sanctions” rewrote its description, which is the text the model reads security
- Tool “submit_request” rewrote its description, which is the text the model reads security
- Schema quality: 68 → 78 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Destructive annotations: pass → 100 functional
- “federal_contract_awards” added an optional parameter “start” cosmetic
- Tool “company_financial_facts” changed its title: Reported financials from SEC filings cosmetic
- Tool “describe_proposition” changed its title: Describe a service cosmetic
- Tool “entity_lookup” changed its title: Company registration lookup (LEI and SEC) cosmetic
- Tool “extract_web_page” changed its title: Read a web page into structure cosmetic
- Tool “federal_contract_awards” changed its title: Search US federal contract actions cosmetic
- Tool “list_propositions” changed its title: List services cosmetic
- Tool “screen_sanctions” changed its title: Screen a name against OFAC sanctions cosmetic
- Tool “submit_request” changed its title: Send a requirement cosmetic
- 3 Nov 26 54
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://services.forevenza.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=forevenza.com | CN=WE1,O=Google Trust Services,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 977dc626c2dbdbd70e6bdde872b9befa |
| SANs: forevenza.com, services.forevenza.com, *.services.forevenza.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of services.forevenza.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| forevenza.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://services.forevenza.com/mcp | Verified | 200 | |
| http (plaintext) | http://services.forevenza.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
company_financial_facts Reported financials from SEC filings ~65
Plumbline: Reported XBRL values of one concept for one SEC filer, with period, form and accession number.
| Name | Type | Req | Description |
|---|---|---|---|
| cik | string | – | – |
| concept | string | – | – |
| taxonomy | string | – | – |
| ticker | string | – | – |
No output schema declared.
No examples provided.
describe_proposition Describe a service ~42
Everything about one service: what happens to a request, what you get, scope and limits, the request fields and any operations.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
entity_lookup Company registration lookup (LEI and SEC) ~73
Plumbline: LEI records and SEC EDGAR registration for a company. Paid per call over HTTP with x402 ($0.02); this tool returns how to call it.
| Name | Type | Req | Description |
|---|---|---|---|
| cik | string | – | – |
| lei | string | – | – |
| name | string | – | – |
| ticker | string | – | – |
No output schema declared.
No examples provided.
extract_web_page Read a web page into structure ~42
Decant: Read one public web page into title, headings, text, links and JSON-LD. robots.txt is honoured.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
federal_contract_awards Search US federal contract actions ~92
Plumbline: US federal contract actions (awards and modifications) by vendor name, NAICS code, place-of-performance state and fiscal year, ten at a time, from FPDS, the government's contract reporting system.
| Name | Type | Req | Description |
|---|---|---|---|
| fiscal_year | integer | – | – |
| naics | string | – | – |
| recipient | string | – | – |
| start | integer | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
list_propositions List services ~37
List every service, with the business it belongs to and a one-line summary: lookups that run instantly, and requirements you can send.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
screen_sanctions Screen a name against OFAC sanctions ~54
Plumbline: Screen a name against the OFAC SDN list and aliases. A match is a lead for review, not a determination.
| Name | Type | Req | Description |
|---|---|---|---|
| min_score | number | – | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
submit_request Send a requirement ~136
Send a requirement to any service, or describe one none of them lists (slug "anything-else"). It is kept with a reference number.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | – |
| budget | object | – | – |
| contact | object | – | Optional; stored apart and deleted after 180 days |
| geography | object | – | – |
| need | string | yes | The requirement in words |
| quantity | object | – | – |
| requested_fields | array | – | – |
| slug | string | yes | Service slug, or anything-else |
| specifications | object | – | Fields from the service's request schema |
| timing | object | – | – |
No output schema declared.
No examples provided.
How do I install the Requirements Desk MCP server?
Requirements Desk is a hosted endpoint at https://services.forevenza.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · services.forevenza.com
claude mcp add --transport http com-forevenza-services-requirements-desk 'https://services.forevenza.com/mcp'
What is the Requirements Desk MCP server?
Requirements Desk is an MCP server listed in the public MCP registry as com.forevenza.services/requirements-desk. Company, sanctions, SEC and federal award lookups, document conversion, and requirement capture. This page covers its hosted endpoint (https://services.forevenza.com/mcp).
Is the Requirements Desk MCP server safe to use?
Requirements Desk scores 62 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Requirements Desk MCP server expose?
Requirements Desk exposes 8 tools: list_propositions, describe_proposition, submit_request, screen_sanctions, company_financial_facts, and 3 more. Their descriptions and schemas cost roughly 541 tokens of context every time the server is loaded.
Does the Requirements Desk MCP server require authentication?
No. We connected to Requirements Desk without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Requirements Desk MCP server still maintained?
Requirements Desk is marked deprecated in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.