EPC Tender Screening MCP (Shiverion/epc-tender-screening-mcp-showcase) is an MCP server listed on the M8ven Trust Index. It scores 56 out of 100, grade D. It declares 11 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
56/100

EPC Tender Screening MCP

An MCP-only server for evidence-based EPC tender screening that enables AI agents to run a full screening workflow, extract requirements, match company profiles, generate compliance matrices, and produce bid/no-bid advisory memos.

→ Shiverion/epc-tender-screening-mcp-showcase· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

Shiverion

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Known vulnerabilities in dependencies: 4 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 2 credentials: MCP_API_KEY, MCP_DEMO_ACCESS_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes11 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

screen_tender

Run the full EPC tender screening workflow: extract requirements, match company profile, generate compliance matrix, and produce bid/no-bid memo.

connect_company_profile_text

Persist uploaded/extracted company profile text as the local company profile used by later screening calls.

connect_current_tender_text

Persist uploaded/extracted tender text as the current local tender used by later screening calls.

connect_tender_source_urls

Persist allowlisted public tender source URLs for later opportunity discovery.

search_public_tenders

Search allowlisted public tender source pages or URLs supplied in the request. This does not crawl the whole internet.

get_data_status

Show which real or example data sources the EPC Tender Screening MCP server is currently using.

extract_tender_requirements

Extract structured EPC tender requirements from tender text. Uses current local tender file if configured.

match_company_profile

Match extracted tender requirements against company capabilities and documents.

generate_compliance_matrix

Generate requirement-by-requirement compliance matrix with evidence, risk, and action.

generate_bid_no_bid_memo

Generate advisory bid/no-bid memo from tender requirements and company profile.

search_historical_proposals

Search local historical proposal examples. Replace the JSON source with your own indexed archive for production.

// known CVEs in dependencies4 high5 medium

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

highnext@16.2.7GHSA-6gpp-xcg3-4w24

Next.js: Middleware / Proxy bypass in App Router applications using Turbopack and single locale

highnext@16.2.7GHSA-89xv-2m56-2m9x

Next.js: Server-Side Request Forgery in Server Actions on custom servers

highnext@16.2.7GHSA-m99w-x7hq-7vfj

Next.js: Denial of Service in App Router using Server Actions

highnext@16.2.7GHSA-p9j2-gv94-2wf4

Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname

mediumnext@16.2.7GHSA-4633-3j49-mh5q

Next.js: Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequences

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configMCP_ALLOW_DEMO_AUTH
configMCP_ALLOW_EXAMPLE_FALLBACKtrue npm run dev
🔐 secretMCP_API_KEYreplace-this-token
🔐 secretMCP_DEMO_ACCESS_TOKENreplace-this-demo-token
configMCP_PUBLIC_BASE_URL
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

11/11 tools missing one or more hints — screen_tender (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); connect_company_profile_text (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); connect_current_tender_text (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +8 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

10/11 tool handlers declare input schemas (91%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tests exist

No test files found

Add tests that exercise each declared tool.

Production dependencies are patched

0 critical, 4 high severity in production deps — next@16.2.7 (high), next@16.2.7 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/shiverion/epc-tender-screening-mcp-showcase?variant=verified)](https://m8ven.ai/mcp/shiverion/epc-tender-screening-mcp-showcase)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 0746b25002e46715473345a010d6613fd39205c1
code hash: 2ccfff7a17dbb7b930e9bd62562acbc3bdd149f85d4889c3ae996e1a987373e6
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client