Skip to content

MCP servers › com.prometiam › risk-mcp

MCP server · registry snapshot 2026-11-06 · last tested 2026-11-06

risk-mcp MCP server

Registry name com.prometiam/risk-mcp

Prometiam Risk Intelligence — the publisher's title

by prometiam.com · domain (the registry's namespace rule)npm ↗Website ↗

Company data and KYB API for 35 countries: monitoring, financial statements, insolvency, sanctions — the publisher's description

3 of 6 record checks metRead-only · tools listed 2026-11-06version 0.4.56MITstandard input/output, streamable HTTP36 tools

Summary

com.prometiam/risk-mcp is a remote and local MCP server listed in the official MCP registry at version 0.4.56, under the namespace of the domain prometiam.com. On 2026-11-06 ProtocolProbe connected to it in read-only mode and read its inventory: 36 tools, 0 resources and 0 prompts.

Record checks

3 of 6 record checks met · 3 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • met: Package names its licence with a standard (SPDX) identifier
  • met: The version the registry lists can be installed and is not withdrawn
  • not met: npm package carries build provenance (attestation)
  • not met: No known critical or high advisory in the package or its dependencies
  • #366 of 18,557 packages by monthly downloads
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs
remote and local package
Transport
standard input/output, streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Package
npm · listed version current
License
MIT
Dependencies
2 packages with a critical or high advisory (0 critical, 2 high)
Tools
36
Last tested
2026-11-06

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-06 (api.prometiam.com), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (0.4.56).

Add to your client

Observed fact

This server accepted a session without any credential and lists 4 tools whose name or declaration suggests they change data (sanctions_watch, sanctions_unwatch, monitor_subscribe, monitor_stop). That is our reading of the names; we did not call them. Source: our connection, 2026-11-06.

Worth knowing before you connect it

  • 2 packages with a critical or high advisory (0 critical, 2 high) in its dependencies (as resolved on 2026-11-06).

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-06
Mode
read-only (no tool calls)
Latest version
0.4.56, published 2026-11-05 (registry, as of the 2026-11-06 snapshot)
First listed version
2026-11-04 (earliest version still in the registry; older removed versions would be earlier)
Version history
2 versions listed, 2026-11-04 to 2026-11-05; 2 in the 90 days before the 2026-11-06 snapshot.
Most recent 2 versions
  • 0.4.56 · 2026-11-05
  • 0.4.55 · 2026-11-04
(versions still listed in the registry only)
Registry data
snapshot 2026-11-06
Package and repository
checked 2026-11-06
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn. Does not apply: repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 0.4.55 (published 2026-11-04) → 0.4.56 (published 2026-11-05), between the registry lists of 2026-11-05 and 2026-11-06.

No release note: the registry entry links no GitHub repository.

Source: the official MCP Registry list on 2026-11-05 and on 2026-11-06; release notes from the GitHub Releases API, checked 2026-11-06.

What it is

What does this server offer?

Observed inventory
36tools
0resources
0prompts

None of its 36 tools are described as changing anything. For 36 the reading was uncertain, so no mark is shown.

  • companies_searchon 1 other server

    “Search companies in official registries by name or identifier.”

    Publisher declares: read-only yes · destructive no · open-world yes

    22 inputs
    • namestring“Company name — fuzzy normalized match.”
    • nifstring“Spanish NIF/CIF — exact match, e.g.”
    • vatstring“VAT number — exact match, with its country prefix or without (ES ESA28015865, FR FR+key+SIREN, PL PL+NIP, NO NO+number+MVA; a malformed or wrong-country value …”
    • abnstring“Australian Business Number (11 digits, e.g.”
    • business_numberstring“Canadian Business Number (CRA, 9 digits, e.g.”
    • sirenstring“French SIREN (9 digits), e.g.”
    • siretstring“French SIRET (14 digits).”
    • nipstring“Polish NIP (10 digits), exact match — use with country PL.”
    • regonstring“Polish REGON (9 or 14 digits), exact match — use with country PL.”
    • oibstring“Croatian OIB (11 digits), exact match — use with country HR.”
    • company_numberstring“Registry identifier — exact match.”
    • leistring“Legal Entity Identifier (20 characters, ISO 17442 check) — exact match, in every live country (resolved through our GLEIF links to the company whose registrati…”
    • register_numberstring“German commercial-register entry, with country DE only: the register type (HRA, HRB, GnR, PR, VR, GsR) and the number, for example HRB12653 or HRB 12653.”
    • register_courtstring“Register court, with register_number and country DE: the city or the Amtsgericht (Frankfurt am Main, Amtsgericht München).”
    • has_risk_flagboolean“Spain only.”
    • risk_flag_typestring“Restrict to one flag type.”
    • statusstring“Filter by the standard status, the same list in every country.”
    • local_statusstring“Filter by the register's own status value (for example dissolved for GB, radiated for FR).”
    • countrystring“Country code: ES (Spain, BORME), FR (France, BODACC), GB (UK, Companies House), IE (Ireland, CRO), PL (Poland, KRS), NO (Norway, Brønnøysundregistrene / Enhets…”
    • limitinteger“Maximum number of results to return (1–100, default 20).”
    • cursorstring“Pagination cursor — pass the previous response's pagination.next_cursor, unchanged, to fetch the next page (a company name search issues o:<n>, the rows alread…”
    • offsetinteger“Name search only: rows of the ranked pool to skip, the same as cursor o:<offset>.”
  • company_detail

    “Fetch a single company by Prometiam internal ID, or by the register's own number: give country and company_number (NIF, SIREN or SIRET, CRN, KRS, CVR, ...; GET /companies/{country}/{company_number}, …”

    Publisher declares: read-only yes · destructive no · open-world yes

    4 inputs
    • idinteger or string“Prometiam internal company ID (integer).”
    • company_numberstring“The register's number for the country (NIF/CIF, SIREN or SIRET, Companies House number, KRS, CVR, ...), instead of id; needs country.”
    • countrystring“Country code: ES (Spain, BORME), FR (France, BODACC), GB (UK, Companies House), IE (Ireland, CRO), PL (Poland, KRS), NO (Norway, Brønnøysundregistrene / Enhets…”
    • includestring“Comma-separated extra blocks: procurement, insolvency, financials, lei, risk_flags, structure, charges — or all (all adds lei and risk_flags; name procurement,…”
  • company_financialson 8 other servers

    “Annual financial statements of a company as filed with the official registers, mapped to one standard chart (revenue, gross profit, operating profit, net profit, assets, cash, equity, liabilities, em…”

    Publisher declares: read-only yes · destructive no · open-world yes

    7 inputs, 1 required
    • idinteger or stringrequired“Prometiam company ID from companies_search; the country is inferred from it.”
    • countrystring“Country code: ES (Spain, BORME), FR (France, BODACC), GB (UK, Companies House), IE (Ireland, CRO), PL (Poland, KRS), NO (Norway, Brønnøysundregistrene / Enhets…”
    • yearsinteger“Fiscal years to return, 1-10 (default 3).”
    • statement_typestring“Default all.”
    • currencystring“Default both.”
    • includestring“lines adds balance_sheet and income_statement with every mapped line.”
    • include_supersededboolean“Also return statements replaced by a later or amended filing, flagged superseded.”
  • events_searchon 2 other servers

    “Search normalized corporate-event records (capital changes, director changes, dissolutions, mergers, insolvency, name changes, etc.) by company, or, with neither company_name nor company_number, as t…”

    Publisher declares: read-only yes · destructive no · open-world yes

    9 inputs
    • company_namestring“Company name — fuzzy match.”
    • company_numberstring“Registry registration number — exact match.”
    • event_typestring“One of new_incorporation, director_change, capital_change, address_change, name_change, merger, demerger, dissolution, liquidation, insolvency, status_change, …”
    • date_fromstring“Filter events on or after this date (YYYY-MM-DD).”
    • date_tostring“Filter events on or before this date (YYYY-MM-DD).”
    • countrystring“Country code: ES (Spain, BORME), FR (France, BODACC), GB (UK, Companies House), IE (Ireland, CRO), PL (Poland, KRS), NO (Norway, Brønnøysundregistrene / Enhets…”
    • limitinteger“Maximum number of results to return (1–100, default 20).”
    • includestring“notice attaches to each event the publication behind it: notice {id, source (BORME, BODACC or Companies House), published_date, reference, type, court, region,…”
    • cursorstring“Pagination cursor — pass the previous response's pagination.next_cursor, unchanged, to fetch the next page (a company name search issues o:<n>, the rows alread…”
  • events_timeline

    “Returns the event history for one company, newest first.”

    Publisher declares: read-only yes · destructive no · open-world yes

    5 inputs
    • company_numberstring“Registry number — exact match (recommended).”
    • company_namestring“Company name — fuzzy match.”
    • countrystring“Country code: ES (Spain, BORME), FR (France, BODACC), GB (UK, Companies House), IE (Ireland, CRO), PL (Poland, KRS), NO (Norway, Brønnøysundregistrene / Enhets…”
    • limitinteger“Maximum events to return (1–200, default 50).”
    • includestring“notice attaches to each event the publication behind it (BORME, BODACC or Companies House), or null for other countries.”
  • event_detailon 1 other server

    “Fetch a single corporate-event record by Prometiam internal ID, with its full before/after values and, with include=notice, the source publication (BORME, BODACC or Companies House; null for other co…”

    Publisher declares: read-only yes · destructive no · open-world yes

    2 inputs, 1 required
    • idinteger or stringrequired“Prometiam internal company-event ID.”
    • includestring“notice attaches the publication behind the event, or null for other countries.”
  • people_searchon 5 other servers

    “Search officers / directors / shareholders by name across EU + UK registries.”

    Publisher declares: read-only yes · destructive no · open-world yes

    4 inputs, 1 required
    • namestringrequired“Person name — normalized pattern match (min 2 characters).”
    • countrystring“Country code: ES (Spain, BORME), FR (France, BODACC), GB (UK, Companies House), IE (Ireland, CRO), PL (Poland, KRS), NO (Norway, Brønnøysundregistrene / Enhets…”
    • limitinteger“Maximum number of results to return (1–100, default 20).”
    • cursorstring“Pagination cursor — pass the previous response's pagination.next_cursor, unchanged, to fetch the next page (a company name search issues o:<n>, the rows alread…”
  • person_detail

    “Fetch a single person (officer / director) by Prometiam internal ID.”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • idinteger or stringrequired“Prometiam internal person ID (integer).”
  • directors_network

    “List directors/officers who sit on many companies (cross-directorship rollup), optionally filtered by name.”

    Publisher declares: read-only yes · destructive no · open-world yes

    6 inputs
    • namestring“Director name filter — trigram match (min 3 characters).”
    • min_companiesinteger“Only return people appointed to at least this many companies (2–100, default 5).”
    • legal_entitiesboolean“If true, include corporate directors (legal entities) instead of only natural persons.”
    • countrystring“Country code: ES (Spain, BORME), FR (France, BODACC), GB (UK, Companies House), IE (Ireland, CRO), PL (Poland, KRS), NO (Norway, Brønnøysundregistrene / Enhets…”
    • limitinteger“Maximum results (1–200, default 50).”
    • offsetinteger“Result offset for pagination.”
  • sanctions_screenon 20 other servers

    “Screen a person or entity name against 44,000+ active sanctions and export-control designations with trigram fuzzy match.”

    Publisher declares: read-only yes · destructive no · open-world yes

    6 inputs, 1 required
    • namestringrequired“Name to screen.”
    • thresholdinteger“Minimum match-confidence percentage (50–100, default 80).”
    • entity_typestring“Restrict to one entity type.”
    • include_pepboolean“Also screen against politically exposed persons (BETA, Spain only, from Wikidata) and return a separate pep block.”
    • pep_min_tierstring“Only return PEP hits at or above this tier.”
    • limitinteger
  • sanctions_entityon 1 other server

    “Fetch full detail for a single sanctions entity by Prometiam internal ID: all aliases, the issuing programme/list, listing date, and identifying data.”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • idinteger or stringrequired“Prometiam internal sanctions-entity ID.”
  • insolvency_search

    “Search insolvency and risk notices (bankruptcies, liquidations, court judgments) by company name or identifier.”

    Publisher declares: read-only yes · destructive no · open-world yes

    11 inputs
    • namestring“Company name — fuzzy match.”
    • vatstring“Spanish NIF/CIF — exact match.”
    • sirenstring“French SIREN (9 digits).”
    • siretstring“French SIRET (14 digits).”
    • company_numberstring“UK Companies House number.”
    • event_typestring“Filter by notice/event type (e.g.”
    • date_fromstring“On or after this date (YYYY-MM-DD).”
    • date_tostring“On or before this date (YYYY-MM-DD).”
    • countrystring“Country code: ES (Spain, BORME), FR (France, BODACC), GB (UK, Companies House), IE (Ireland, CRO), PL (Poland, KRS), NO (Norway, Brønnøysundregistrene / Enhets…”
    • limitinteger“Maximum number of results to return (1–100, default 20).”
    • cursorstring“Pagination cursor — pass the previous response's pagination.next_cursor, unchanged, to fetch the next page (a company name search issues o:<n>, the rows alread…”
Show 24 more tools
  • insolvency_notices_search

    “Search CORPORATE insolvency notices published in official gazettes and registers across France, Germany, the UK, Austria, Switzerland, Norway, Finland, the US, the Netherlands, Denmark, Croatia, Swed…”

    Publisher declares: read-only yes · destructive no · open-world yes

    7 inputs
    • namestring“Company name — matched anywhere in the normalized name (min 2 characters).”
    • countrystring“Insolvency-coverage country.”
    • event_typestring“Notice type, e.g.”
    • date_fromstring“Filing date on or after this date (YYYY-MM-DD).”
    • date_tostring“Filing date on or before this date (YYYY-MM-DD).”
    • limitinteger“Maximum number of results to return (1–100, default 20).”
    • cursorstring“Pagination cursor — pass the previous response's pagination.next_cursor, unchanged, to fetch the next page (a company name search issues o:<n>, the rows alread…”
  • procurement_awards

    “List public-contract awards by supplier, buyer, supplier tax id, CPV code and date, newest first.”

    Publisher declares: read-only yes · destructive no · open-world yes

    11 inputs
    • countrystring“Restrict to one country; omit for all countries.”
    • company_idinteger or string“Prometiam company id of the supplier (from companies_search).”
    • nifstring“Supplier identifier as published, exact match: NIF/CIF (Spain), SIRET (France), Companies House number (United Kingdom), CRO number (Ireland), NIP or KRS (Pola…”
    • supplierstring“Supplier name, matched anywhere (min 3 characters).”
    • buyerstring“Contracting body name, matched anywhere (min 3 characters), e.g.”
    • cpvstring“CPV code or prefix, 2-8 digits (45 = construction works).”
    • date_fromstring“Award date on or after (YYYY-MM-DD).”
    • date_tostring“Award date on or before (YYYY-MM-DD).”
    • min_amountnumber“Minimum awarded amount in EUR.”
    • limitinteger“Maximum number of results to return (1–100, default 20).”
    • cursorstring“Pagination cursor — pass the previous response's pagination.next_cursor, unchanged, to fetch the next page (a company name search issues o:<n>, the rows alread…”
  • procurement_buyer

    “Risk profile of a PUBLIC BUYER (a contracting body) in Spain or France — BETA.”

    Publisher declares: read-only yes · destructive no · open-world yes

    2 inputs, 1 required
    • idstringrequired“National identifier of the contracting body: DIR3 code or NIF (Spain), SIRET (France).”
    • countrystring“Defaults to ES.”
  • procurement_buyers

    “List scored public buyers (contracting bodies) in Spain or France ordered by one buyer score, highest first — BETA.”

    Publisher declares: read-only yes · destructive no · open-world yes

    7 inputs
    • countrystring“Defaults to ES.”
    • modelstring“Which score orders the list (default competition).”
    • min_scoreinteger“Keep buyers at or above this score.”
    • namestring“Buyer name, matched anywhere (min 3 characters).”
    • regionstring“Region name, matched anywhere.”
    • limitinteger“Maximum number of results to return (1–100, default 20).”
    • cursorstring“Pagination cursor — pass the previous response's pagination.next_cursor, unchanged, to fetch the next page (a company name search issues o:<n>, the rows alread…”
  • procurement_relationship

    “How dependent a public buyer and one of its five largest suppliers are on each other (Spain or France, BETA): awards, awarded value, the supplier's share of the buyer's awarded value, first/last awar…”

    Publisher declares: read-only yes · destructive no · open-world yes

    3 inputs, 2 required
    • buyerstringrequired“National identifier of the contracting body (DIR3/NIF for Spain, SIRET for France).”
    • supplierstringrequired“Supplier tax id (NIF for Spain, SIREN for France).”
    • countrystring“Defaults to ES.”
  • sanctions_watch

    “Add a name to your sanctions watchlist (sanctions_watch scope, Starter and above): the API re-screens it against every list update and reports new hits on sanctions_watchlist, or calls webhook_url wh…”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes

    3 inputs, 1 required
    • namestringrequired“Name to watch.”
    • entity_typestring
    • webhook_urlstring“https URL called when a new hit appears.”
  • sanctions_unwatch

    “Remove one of your sanctions watchlist entries by id (from sanctions_watchlist).”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Watchlist entry id.”
  • company_by_identifier

    “Find ONE company from an identifier, the country worked out for you (GET /companies/by-identifier, 1 credit, answered like company_detail with the same include).”

    Publisher declares: read-only yes · destructive no · open-world yes

    4 inputs, 2 required
    • typestringrequired“The kind of identifier in value.”
    • valuestringrequired“The VAT number, the 20-character LEI or the register company number.”
    • countrystring“Required with type=company_number and with a VAT number that has no prefix; optional otherwise.”
    • includestring“Extra blocks to attach, as on company_detail.”
  • companies_lookup

    “Resolve up to 100 companies in ONE call (POST /companies/lookup).”

    Publisher declares: read-only yes · destructive no · open-world yes

    2 inputs, 1 required
    • itemsarrayrequired“Up to 100 companies to resolve.”
    • idempotency_keystring“Optional.”
  • sanctions_screen_batchon 1 other server

    “Screen up to 50 names against the sanctions lists in ONE call (POST /sanctions/screen).”

    Publisher declares: read-only yes · destructive no · open-world yes

    7 inputs, 1 required
    • namesarrayrequired“Names to screen (people, companies, vessels).”
    • thresholdinteger“Minimum similarity 30-100 (default 80).”
    • groupstring“entity: one row per listed person/company with lists[] and sources[] instead of one row per source list.”
    • liststring“Comma-separated source lists to restrict to, e.g.”
    • active_onlyboolean“Only currently listed entries (default true).”
    • limitinteger“Hits returned per name (default 10).”
    • idempotency_keystring“Optional.”
  • insolvency_check

    “Check up to 100 counterparties for CORPORATE insolvency notices in ONE call (POST /insolvency/check) across FR, DE, GB, AT, CH, NO, FI, US, NL, DK, HR, SE, ES, LV, EE and SG.”

    Publisher declares: read-only yes · destructive no · open-world yes

    2 inputs, 1 required
    • itemsarrayrequired“Up to 100 counterparties to check.”
    • idempotency_keystring“Optional.”
  • insolvency_record

    “Fetch a single insolvency / risk notice by Prometiam internal ID, with related corporate events.”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • idinteger or stringrequired“Prometiam internal insolvency-record ID.”
  • “Returns dataset coverage statistics: per-country company count, event count, person count, latest filing date, and data sources.”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • “Returns the calling API key's account info and current usage: plan tier, rate limits (per minute in requests, per day / month in credits), credits used and left, and enabled scopes.”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • vat_validateon 4 other servers

    “Validate an EU VAT number against VIES (the European Commission's VAT Information Exchange System) and return the registered trader name and address when valid.”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • vatstringrequired“Full VAT number including the 2-letter country prefix, e.g.”
  • “Look up a Legal Entity Identifier (LEI) in the GLEIF global register by its 20-character ISO 17442 code.”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • leistringrequired“20-character alphanumeric LEI, e.g.”
  • lei_search

    “Search the GLEIF global LEI register by legal-entity name (full-text).”

    Publisher declares: read-only yes · destructive no · open-world yes

    2 inputs, 1 required
    • namestringrequired“Legal entity name to search for.”
    • limitinteger“Maximum candidates to return (1–25, default 10).”
  • lei_relationships

    “GLEIF Level 2 corporate ownership ("who owns whom") for a 20-character LEI: its direct parent, ultimate parent, and direct children — each with LEI, legal name, jurisdiction, status, and city/country.”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • leistringrequired“20-character alphanumeric LEI, e.g.”
  • monitor_liston 3 other servers

    “List the companies currently subscribed to ongoing monitoring for this API key, with their labels and last-alert timestamps.”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • “Get one monitored company by its monitor ID, including its alert history (events/status/sanctions matches detected since subscription).”

    Publisher declares: read-only yes · destructive no · open-world no

    1 input, 1 required
    • idinteger or stringrequired“Monitor subscription ID (from monitor_subscribe or monitor_list).”
  • monitor_subscribe

    “Subscribe a company to ongoing monitoring.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes

    5 inputs, 2 required
    • company_idinteger or stringrequired“Prometiam internal company ID to monitor (from companies_search / company_detail).”
    • webhook_urlstringrequired“HTTPS URL that receives signed alert POSTs.”
    • countrystring“Country of the company to monitor: ES (default), GB, IE, PL, NO, FI, SE, BE, HR, DK, EE, SK, CH, LV, CY, RO, LT, CA, AU, JP, IL, SG, CO, TW, BR, CZ, DE, NL, AR…”
    • labelstring“Optional human-friendly label for this subscription.”
    • eventsarray“Optional list of event types to filter alerts to (default: all).”
  • monitor_stop

    “Stop monitoring a company and delete its subscription by monitor ID.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • idinteger or stringrequired“Monitor subscription ID to delete.”
  • sanctions_changeson 1 other server

    “List additions, removals and amendments detected on the sanctions lists, newest first.”

    Publisher declares: read-only yes · destructive no · open-world yes

    4 inputs
    • sincestring“ISO date (YYYY-MM-DD).”
    • change_typestring“Restrict to one kind of change.”
    • liststring“Comma-separated source lists, e.g.”
    • limitinteger“Maximum changes to return (1–100, default 20).”
  • sanctions_watchlist

    “Return your sanctions watchlists and any recent hits against them.”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-06.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
99% of 144
Tools with a description
100% of 36
Typical description length
1,111 characters

The tool set

Counted from the listing

Tools
36
Size of the list
about 93,006 tokens for an agent to load (characters ÷ 4)
Naming
34 of 36 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 36 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the npm package prometiam-risk-mcp

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
  "mcpServers": {
    "risk-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "prometiam-risk-mcp@0.4.56"
      ]
    }
  }
}
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "risk-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "prometiam-risk-mcp@0.4.56"
      ]
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "risk-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "prometiam-risk-mcp@0.4.56"
      ]
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"risk-mcp","type":"stdio","command":"npx","args":["-y","prometiam-risk-mcp@0.4.56"]}'
Claude Code
claude mcp add --transport stdio risk-mcp -- npx -y prometiam-risk-mcp@0.4.56
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "risk-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "prometiam-risk-mcp@0.4.56"
      ],
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "risk-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "prometiam-risk-mcp@0.4.56"
      ]
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.risk-mcp]
command = "npx"
args = ["-y", "prometiam-risk-mcp@0.4.56"]
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "risk-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "prometiam-risk-mcp@0.4.56"
      ]
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- npx -y prometiam-risk-mcp@0.4.56
  • Optional settings the entry also lists (left out above): PROMETIAM_API_KEY, PROMETIAM_BASE_URL.
  • This runs the publisher's code on your machine (npx). Read its README first.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-06 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://api.prometiam.com/functions/v1/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "risk-mcp": {
      "url": "https://api.prometiam.com/functions/v1/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "risk-mcp": {
      "type": "http",
      "url": "https://api.prometiam.com/functions/v1/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"risk-mcp","type":"http","url":"https://api.prometiam.com/functions/v1/mcp"}'
Claude Code
claude mcp add --transport http risk-mcp https://api.prometiam.com/functions/v1/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "risk-mcp": {
      "type": "streamableHttp",
      "url": "https://api.prometiam.com/functions/v1/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "risk-mcp": {
      "httpUrl": "https://api.prometiam.com/functions/v1/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.risk-mcp]
url = "https://api.prometiam.com/functions/v1/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "risk-mcp": {
      "url": "https://api.prometiam.com/functions/v1/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://api.prometiam.com/functions/v1/mcp --transport http
  • Optional settings the entry also lists (left out above): Authorization.
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists
0.4.56
Latest stable
0.4.56
Status
current
Withdrawn
no

Source: registry.npmjs.org · 2026-11-06. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

critical0high2moderate0low0

Counted in the full dependency tree as resolved on 2026-11-06 (npm audit; each bar counts packages with an advisory, not advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity
sha512-F1kj27oUP/VMg027E…
Signature
signed
License
MIT

Source: the package registry · 2026-11-06.

Usage

Downloads
6,442 in the last month

Source: api.npmjs.org · 2026-11-06.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint api.prometiam.com/functions/v1/mcpSession openedmatchesour test · 2026-11-06
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-06
Version 0.4.56 on npmExists and can be installedmatchesnpm · 2026-11-06

Tool list changes

Our reads compared · no tool called

Hosted endpoint api.prometiam.com/functions/v1/mcp

1 of 1 comparison between consecutive reads showed a change (2 reads, 2026-11-05 to 2026-11-06; versions 0.4.55 to 0.4.56).

Last change seen between our reads on 2026-11-05 (version 0.4.55) and 2026-11-06 (version 0.4.56).

Changed (10):

companies_lookup: input schemacompanies_search: description, input schemacompany_detail: description, input schemacompany_financials: input schemadirectors_network: input schemaevents_search: input schemaevents_timeline: input schemainsolvency_search: input schemamonitor_subscribe: descriptionpeople_search: description, input schema

Compared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-11-06 is not known yet. No tool was called. How it is compared

Choosing

Record checks

Public records · not a safety rating

3 of 6 record checks met · 3 do not apply

  • #366 of 18,557 packages by monthly downloads
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • MetPackage names its licence with a standard (SPDX) identifierMIT
  • MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
  • Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.What changes this check: npm's documentation describes publishing with provenance from a cloud-hosted runner of a supported CI/CD provider, using npm CLI 9.5.0 or newer and npm publish --provenance. npm: generating provenance statements
  • Not metNo known critical or high advisory in the package or its dependencies2 packages in its dependencies with a critical or high advisory (npm audit counts packages, not advisories).What changes this check: npm's documentation describes listing a project's dependency advisories with npm audit and applying compatible dependency updates. npm: npm audit

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-06. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about com.prometiam/risk-mcp

Answered from the data above

Who publishes com.prometiam/risk-mcp?

The registry ties the namespace com.prometiam to the domain prometiam.com; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Is com.prometiam/risk-mcp safe to install?

We do not rate servers as safe or unsafe. 3 of its 6 applicable record checks are met (facts from public records, each listed on this page). What the records show: The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has packages with advisories (2 high; npm audit). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does com.prometiam/risk-mcp need an API key or sign-in?

It opened a session without any credential on 2026-11-06. The registry entry declares no required credential; no declaration is not a guarantee.

Has com.prometiam/risk-mcp been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Is the listed version current?

Yes. The registry lists 0.4.56, the latest stable release on npm.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-06
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-11-06, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 4,093 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 36 tools, 0 resources, 0 prompts.
  4. 6,031 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added in a later update
listed 2026-11-06; not classified yet
Pricing modelAI-classified
pending: added in a later update
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-11-06
MCP capability
tools
our test · 2026-11-06
Transport
standard input/output, streamable HTTP
registry · 2026-11-06
Required credentials
none declared
registry · 2026-11-06 · no declaration is not a guarantee
Package registry
registry · 2026-11-06
Freshness
0–30 days
registry updatedAt · 2026-11-06
Lifecycle status
registry · 2026-11-06
License class
package registry · 2026-11-06
Integrity hash
declared (sri)
package registry · 2026-11-06
Signature / provenance
signed
package registry · 2026-11-06
Dependency advisories
high
npm audit · 2026-11-06
Popularity
6,442 downloads a month
package registry · 2026-11-06
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
either (remote or your machine)
where it runs, from the hosting type · 2026-11-06

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “com.prometiam/risk-mcp: MCP server record.” Data checked 2026-11-06. https://protocolprobe.com/mcp/servers/com.prometiam/risk-mcp

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 3 of 6 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/com.prometiam/risk-mcp)](https://protocolprobe.com/mcp/servers/com.prometiam/risk-mcp)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology