EntityFeed
REMOTE · ENTITYFEED.COM
Company lookups in the official registers of Slovakia and Czechia, with the source on each record.
Available components
Last scanned (8 hours ago)
Scores higher than 73% of remote servers
Reachable. Last reached 6 Nov 2026.
Category CRM and Sales
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 Security89
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 288 tokens (~144/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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 (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 6 Nov 26 +3
- HSTS header: fail → pass ▲ security
- Tool “get_company” rewrote its description, which is the text the model reads security
- Tool “search_company” rewrote its description, which is the text the model reads security
- Schema quality: 100 → 144 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- 5 Nov 26 75
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 6 Nov 2026 · Probed https://entityfeed.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=entityfeed.com | CN=YE1,O=Let's Encrypt,C=US | 5 Nov 2026 | 3 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 65289685aa0637aae8938984732b6013769 |
| SANs: *.entityfeed.com, entityfeed.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of entityfeed.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| entityfeed.com. | 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="mcp"
Bearer realm="mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
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://entityfeed.com/mcp | Verified | 200 | |
| http (plaintext) | http://entityfeed.com/mcp | HTTPS enforced | 308 | https://entityfeed.com/mcp |
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 →
get_company Get one company by ID ~130
Fetch one company from the official register of the given country by its ID. Returns the unified record with status, address, legal form, activities, `source` and `retrieved_at`. Slovak legal persons come from a copy of the register that is updated every day: then `source.snapshot_date` is set and `retrieved_at` is the date of the newest batch applied. Other Slovak entries are fetched live.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | SK = Slovakia (RPO), CZ = Czechia (ARES). |
| id | string | yes | Company ID in the register of the given country. |
No output schema declared.
No examples provided.
search_company Search companies by name or ID ~158
Search official company registers by name, or by company ID. Returns up to 10 matches in one unified schema, each with `source` and `retrieved_at`. Slovak legal persons come from a copy of the register that is updated every day: those records have `source.snapshot_date`, and `retrieved_at` is the date of the newest batch applied. Use get_company for the detail of a single company.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | SK = Slovakia (RPO), CZ = Czechia (ARES). |
| include_inactive | boolean | – | SK only: also return terminated entities. |
| limit | integer | – | Maximum number of results. |
| query | string | yes | Company name (or part of it) or an ID. |
No output schema declared.
No examples provided.
How do I install the EntityFeed MCP server?
EntityFeed is a hosted endpoint at https://entityfeed.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.
remote · entityfeed.com
claude mcp add --transport http com-entityfeed-companies 'https://entityfeed.com/mcp'
What is the EntityFeed MCP server?
EntityFeed is an MCP server listed in the public MCP registry as com.entityfeed/companies. Company lookups in the official registers of Slovakia and Czechia, with the source on each record. This page covers its hosted endpoint (https://entityfeed.com/mcp).
Is the EntityFeed MCP server safe to use?
EntityFeed scores 78 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 EntityFeed MCP server expose?
EntityFeed exposes 2 tools: search_company, get_company. Their descriptions and schemas cost roughly 288 tokens of context every time the server is loaded.
Does the EntityFeed MCP server require authentication?
Yes. EntityFeed 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 EntityFeed MCP server still maintained?
EntityFeed is still listed as active in the MCP registry. We last reached this channel on 6 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 EntityFeed MCP server?
VerifyMCP ran 13 checks on EntityFeed, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.