# Requirements Desk (remote · services.forevenza.com)

Company, sanctions, SEC and federal award lookups, document conversion, and requirement capture.

- Trust score: 62/100 (medium)
- Registry status: deprecated
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

> **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."

## Components

- remote · `services.forevenza.com`: 62/100 (this document), [markdown](https://verifymcp.io/servers/com-forevenza-services-requirements-desk/services.md), [page](https://verifymcp.io/servers/com-forevenza-services-requirements-desk/services)

## Channel facts

- Endpoint: `https://services.forevenza.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 630 tokens (~78/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 72/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 15% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-forevenza-services-requirements-desk 'https://services.forevenza.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-forevenza-services-requirements-desk": {
      "url": "https://services.forevenza.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-forevenza-services-requirements-desk": {
      "type": "http",
      "url": "https://services.forevenza.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-forevenza-services-requirements-desk]
url = "https://services.forevenza.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-forevenza-services-requirements-desk": {
      "type": "remote",
      "url": "https://services.forevenza.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-forevenza-services-requirements-desk --url 'https://services.forevenza.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-forevenza-services-requirements-desk:
    url: "https://services.forevenza.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-forevenza-services-requirements-desk": {
      "Transport": "http",
      "Url": "https://services.forevenza.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-forevenza-services-requirements-desk -t streamable-http -u 'https://services.forevenza.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-forevenza-services-requirements-desk": {
      "type": "http",
      "url": "https://services.forevenza.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 62, +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.

### 2026-11-04 (score 61, +7)

- [security improvement] 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
- [functional regression] Schema quality: 68 → 78
- [functional improvement] Stability: unverified → 0.03
- [functional] Destructive annotations: pass → 100
- [cosmetic] “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

### 2026-11-03 (score 54)

First indexed and scored.

## MCP tools (8)

### `list_propositions` (~37 tokens)

List services

List every service, with the business it belongs to and a one-line summary: lookups that run instantly, and requirements you can send.

### `describe_proposition` (~42 tokens)

Describe a service

Everything about one service: what happens to a request, what you get, scope and limits, the request fields and any operations.

Input parameters:

- `slug` (string, required)

### `submit_request` (~136 tokens)

Send a requirement

Send a requirement to any service, or describe one none of them lists (slug "anything-else"). It is kept with a reference number.

Input parameters:

- `action` (string)
- `budget` (object)
- `contact` (object): Optional; stored apart and deleted after 180 days
- `geography` (object)
- `need` (string, required): The requirement in words
- `quantity` (object)
- `requested_fields` (array)
- `slug` (string, required): Service slug, or anything-else
- `specifications` (object): Fields from the service's request schema
- `timing` (object)

### `screen_sanctions` (~54 tokens)

Screen a name against OFAC sanctions

Plumbline: Screen a name against the OFAC SDN list and aliases. A match is a lead for review, not a determination.

Input parameters:

- `min_score` (number)
- `name` (string, required)

### `company_financial_facts` (~65 tokens)

Reported financials from SEC filings

Plumbline: Reported XBRL values of one concept for one SEC filer, with period, form and accession number.

Input parameters:

- `cik` (string)
- `concept` (string)
- `taxonomy` (string)
- `ticker` (string)

### `federal_contract_awards` (~92 tokens)

Search US federal contract actions

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.

Input parameters:

- `fiscal_year` (integer)
- `naics` (string)
- `recipient` (string)
- `start` (integer)
- `state` (string)

### `extract_web_page` (~42 tokens)

Read a web page into structure

Decant: Read one public web page into title, headings, text, links and JSON-LD. robots.txt is honoured.

Input parameters:

- `url` (string, required)

### `entity_lookup` (~73 tokens)

Company registration lookup (LEI and SEC)

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.

Input parameters:

- `cik` (string)
- `lei` (string)
- `name` (string)
- `ticker` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-forevenza-services-requirements-desk/services#diagnostics

## Score history

- 2026-11-05: 62
- 2026-11-04: 61
- 2026-11-03: 54

## Common questions

### 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.

## Links

- Remote endpoint: https://services.forevenza.com/mcp
- Website: https://services.forevenza.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-forevenza-services-requirements-desk/services.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-forevenza-services-requirements-desk/services.json
- HTML version of this page: https://verifymcp.io/servers/com-forevenza-services-requirements-desk/services