TenderScope
REMOTE · TENDERSCOPE.APP
Public tenders (EU TED, Armenia) for AI agents: search, details, watchlists, alerts.
Available components
Last scanned (9 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
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 Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- 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 Usability66
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 +2
- 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 security
- Schema quality: 190 → 236 ▼ functional
- Tool coverage: 83% → 100% ▲ functional
- Schema quality: good → excellent functional
- Server version: 1.3.0 → 1.4.0 functional
- “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 cosmetic
- 22 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 21 Oct 26 67
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://tenderscope.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tenderscope.app | CN=WE1,O=Google Trust Services,C=US | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 828d3ba28a0100171347b71331948f78 |
| SANs: tenderscope.app, www.tenderscope.app, *.www.tenderscope.app | ||||||
| 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 tenderscope.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| tenderscope.app. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="tenderscope-mcp"
Bearer realm="tenderscope-mcp"Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | No resource metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tenderscope.app/mcp | Verified | 200 | |
| http (plaintext) | http://tenderscope.app/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 →
add_to_watchlist Add tender watchlist ~179
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | Watchlist name |
| Name | Type | Req | Description |
|---|---|---|---|
| estimatedMatches | integer | yes | Open tenders matching the filters right now |
| hint | string | – | Note about the filters, e.g. which currency the budget range uses |
| watchlistId | string | yes | – |
No examples provided.
get_deadline_alerts Get deadline alerts ~60
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| alerts | array | yes | – |
| hint | string | – | – |
No examples provided.
get_tender Get tender details ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Tender id from search_tenders results |
| Name | Type | Req | Description |
|---|---|---|---|
| budget | – | yes | Estimated budget as a decimal string, e.g. "125000.00" |
| budgetNote | string | – | Why budget is null; present only when it is |
| buyer | string|null | yes | – |
| country | string|null | yes | ISO 3166-1 alpha-2 |
| cpvCodes | array | – | Omitted on the Free plan |
| currency | string|null | yes | ISO 4217 |
| deadline | – | yes | Submission deadline, ISO 8601 UTC |
| docsUrl | array | – | Links to tender documents; omitted on the Free plan |
| hint | string | – | – |
| id | string | yes | – |
| lots | array | – | Omitted on the Free plan |
| lotsCount | – | yes | – |
| okpd2Codes | array | – | OKPD2 codes (EAEU sources); omitted on the Free plan |
| publishedAt | – | yes | – |
| region | string|null | yes | – |
| source | string | yes | – |
| status | string | yes | – |
| 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 | yes | – |
| updatedAt | string | yes | – |
| url | string | yes | – |
No examples provided.
search_tenders Search public tenders ~387
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Free-text query in English, Russian or Armenian, e.g. "IT services, deadline > week" |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
No examples provided.
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.
remote · tenderscope.app
claude mcp add --transport http marutmarutyan-tenderscope 'https://tenderscope.app/mcp'
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.