# TenderScope (remote · tenderscope.app)

Public tenders (EU TED, Armenia) for AI agents: search, details, watchlists, alerts.

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `tenderscope.app`: 75/100 (this document), [markdown](https://verifymcp.io/servers/marutmarutyan-tenderscope/tenderscope.md), [page](https://verifymcp.io/servers/marutmarutyan-tenderscope/tenderscope)

## Channel facts

- Endpoint: `https://tenderscope.app/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.4.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**: 71/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - 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**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 946 tokens (~236/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 TenderScope MCP server?

TenderScope is a hosted endpoint at https://tenderscope.app/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 marutmarutyan-tenderscope 'https://tenderscope.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "marutmarutyan-tenderscope": {
      "url": "https://tenderscope.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "marutmarutyan-tenderscope": {
      "type": "http",
      "url": "https://tenderscope.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.marutmarutyan-tenderscope]
url = "https://tenderscope.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "marutmarutyan-tenderscope": {
      "type": "remote",
      "url": "https://tenderscope.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add marutmarutyan-tenderscope --url 'https://tenderscope.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  marutmarutyan-tenderscope:
    url: "https://tenderscope.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "marutmarutyan-tenderscope": {
      "Transport": "http",
      "Url": "https://tenderscope.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add marutmarutyan-tenderscope -t streamable-http -u 'https://tenderscope.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "marutmarutyan-tenderscope": {
      "type": "http",
      "url": "https://tenderscope.app/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-04 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 70, +2)

- [security] Tool “add_to_watchlist” rewrote its description, which is the text the model reads
- [security] Tool “get_deadline_alerts” rewrote its description, which is the text the model reads
- [security] Tool “get_tender” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 190 → 236
- [functional improvement] Tool coverage: 83% → 100%
- [functional] Schema quality: good → excellent
- [functional] Server version: 1.3.0 → 1.4.0
- [cosmetic] “add_to_watchlist” reworded the description of “channels”
- [cosmetic] “add_to_watchlist” reworded the description of “filters”
- [cosmetic] Tool “add_to_watchlist” changed its title: Add tender watchlist
- [cosmetic] Tool “get_deadline_alerts” changed its title: Get deadline alerts
- [cosmetic] Tool “get_tender” changed its title: Get tender details
- [cosmetic] Tool “search_tenders” changed its title: Search public tenders

### 2026-10-22 (score 68, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-21 (score 67)

First indexed and scored.

## MCP tools (4)

### `search_tenders` (~387 tokens)

Search public tenders

Search open public procurement tenders (government tenders, госзакупки, тендеры) from official portals: EU TED and Armenia ARMEPS (armeps.am, gnumner.am). Free text in English, Russian or Armenian, optional filters: country, CPV/OKPD2 codes, budget, deadline. Returns up to 20 short cards; "subject" lists the lot names when the title alone does not say what is procured. Words are matched in the title, lot names and buyer. Budgets are in each tender's own currency (Armenia: AMD, from the invitation document); to compare budgets across countries, set budgetCurrency (e.g. "EUR") with minBudget/maxBudget.

Input parameters:

- `budgetCurrency` (string): Currency of minBudget/maxBudget (ISO 4217). When set, each tender budget is converted at fixed reference rates (updated quarterly), so EU (EUR, PLN, SEK…), Armenian (AMD) and Russian (RUB) tenders co…
- `countries` (array): Buyer countries, ISO 3166-1 alpha-2 (e.g. ["DE", "AM"])
- `cpv` (array): CPV codes or prefixes (e.g. ["72", "48"])
- `deadlineAfter`: Only tenders whose deadline is after this ISO 8601 date/datetime
- `limit` (integer): Number of results, 1–20 (default 10)
- `maxBudget` (number): Maximum estimated budget, in the tender currency
- `minBudget` (number): Minimum estimated budget, in the tender currency
- `q` (string, required): Free-text query in English, Russian or Armenian, e.g. "IT services, deadline > week"

Output parameters:

- `budgetNote` (string): Why some results have budget null (not published or not yet read); present only when some do
- `degradedSources` (array): Sources currently failing; data may be stale
- `hint` (string): How to broaden the query when there are few or no results
- `results` (array)

### `get_tender` (~82 tokens)

Get tender details

Get the full card of one tender: status, deadline, budget, what is procured (subject), lots with prices and CPV codes, links to tender documents. Use the id from search_tenders results. On the Free plan, CPV codes, lots and document links are omitted.

Input parameters:

- `id` (string, required): Tender id from search_tenders results

Output parameters:

- `budget`: Estimated budget as a decimal string, e.g. "125000.00"
- `budgetNote` (string): Why budget is null; present only when it is
- `buyer` (string|null)
- `country` (string|null): ISO 3166-1 alpha-2
- `cpvCodes` (array): Omitted on the Free plan
- `currency` (string|null): ISO 4217
- `deadline`: Submission deadline, ISO 8601 UTC
- `docsUrl` (array): Links to tender documents; omitted on the Free plan
- `hint` (string)
- `id` (string)
- `lots` (array): Omitted on the Free plan
- `lotsCount`
- `okpd2Codes` (array): OKPD2 codes (EAEU sources); omitted on the Free plan
- `publishedAt`
- `region` (string|null)
- `source` (string)
- `status` (string)
- `subject` (string): What is procured: lot names from the tender (for Armenian tenders, from the invitation document), in the original language (e.g. Armenian), separated by "; ". Omitted when unknown or the same as the…
- `title` (string)
- `updatedAt` (string)
- `url` (string)

### `add_to_watchlist` (~179 tokens)

Add tender watchlist

Save a query and filters as a watchlist for ongoing monitoring; new, amended and closing-soon matching tenders are then sent by email (Free plan: daily digest) and/or a signed HTTPS webhook (Pro plan). Returns watchlistId and how many open tenders match right now. Each call creates a new watchlist (the number per plan is limited); manage or delete watchlists in the dashboard.

Input parameters:

- `channels` (object): Where alerts go: email (default) and/or an HTTPS webhook; webhooks need the Pro plan, Free gets a daily email digest
- `filters` (object, required): Which tenders to watch: the same query and filters as search_tenders (q, countries, cpv, budget, deadlineAfter); filters that match every tender are rejected
- `name` (string, required): Watchlist name

Output parameters:

- `estimatedMatches` (integer): Open tenders matching the filters right now
- `hint` (string): Note about the filters, e.g. which currency the budget range uses
- `watchlistId` (string)

### `get_deadline_alerts` (~60 tokens)

Get deadline alerts

List alerts from your watchlists for the last 30 days on tenders that are still open, nearest deadline first (up to 50). Does not mark alerts as read. Empty until you create a watchlist with add_to_watchlist.

Output parameters:

- `alerts` (array)
- `hint` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/marutmarutyan-tenderscope/tenderscope#diagnostics

## Score history

- 2026-11-05: 75
- 2026-11-04: 75
- 2026-11-03: 74
- 2026-11-02: 74
- 2026-11-01: 73
- 2026-10-31: 73
- 2026-10-30: 72
- 2026-10-29: 72
- 2026-10-28: 72
- 2026-10-27: 71
- 2026-10-26: 71
- 2026-10-25: 70
- 2026-10-24: 70
- 2026-10-23: 68
- 2026-10-22: 68
- 2026-10-21: 67

## Common questions

### What is the TenderScope MCP server?

TenderScope is an MCP server listed in the public MCP registry as io.github.MarutMarutyan/tenderscope. Public tenders (EU TED, Armenia) for AI agents: search, details, watchlists, alerts. This page covers its hosted endpoint (https://tenderscope.app/mcp).

### Is the TenderScope MCP server safe to use?

TenderScope scores 75 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 TenderScope MCP server expose?

TenderScope exposes 4 tools: search_tenders, get_tender, add_to_watchlist, get_deadline_alerts. Their descriptions and schemas cost roughly 708 tokens of context every time the server is loaded.

### Does the TenderScope MCP server require authentication?

Yes. TenderScope asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the TenderScope MCP server still maintained?

TenderScope is still listed as active 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.

### What did VerifyMCP test on the TenderScope MCP server?

VerifyMCP ran 12 checks on TenderScope, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about TenderScope: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://tenderscope.app/mcp
- Authorisation metadata: https://tenderscope.app/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/MarutMarutyan/tenderscope-lite
- Website: https://tenderscope.app/
- Changelog RSS feed: https://verifymcp.io/servers/marutmarutyan-tenderscope/tenderscope.xml
- Changelog JSON feed: https://verifymcp.io/servers/marutmarutyan-tenderscope/tenderscope/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/marutmarutyan-tenderscope/tenderscope.json
- HTML version of this page: https://verifymcp.io/servers/marutmarutyan-tenderscope/tenderscope