Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

EnrichGrid

REMOTE · ENRICHGRID.COM

LinkedIn person, company and school data plus people search for AI agents. Pay per found profile.

Available components

+3 this week 82 Trust /100

Last scanned (16 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 414 tokens (~69/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 83% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

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 →

Changelog

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.

  • 21 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 26 +1

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

  • 14 Nov 26 +1

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

  • 12 Nov 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.

  • 10 Nov 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.

  • 8 Nov 26 +1

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

  • 6 Nov 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 21 Nov 2026 · Probed https://enrichgrid.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=enrichgrid.com CN=YE2,O=Let's Encrypt,C=US 3 Nov 2026 1 Feb 2027 ECDSA 256 ECDSA-SHA384 6d29ba6bb6a4cfc126de7189d0a1ba47b80
SANs: enrichgrid.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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 enrichgrid.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
enrichgrid.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
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

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://enrichgrid.com/mcp Verified 200
http (plaintext) http://enrichgrid.com/mcp HTTPS enforced 308 https://enrichgrid.com/mcp
MCP tools · 6 exposed · ~375 tokens

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 →

Tool Tokens
enrich_company ~63

Get a company's firmographics from a LinkedIn company URL, slug or numeric ID: industry, headcount, website, HQ, founding year, specialties, description. 1 credit if found.

NameTypeReqDescription
identifierstringyesLinkedIn URL, slug or numeric/profile ID

No output schema declared.

No examples provided.

enrich_person ~63

Get a person's professional profile from a LinkedIn profile URL, slug or ID: name, headline, current title and company, location, full work experience and education. 1 credit if found.

NameTypeReqDescription
identifierstringyesLinkedIn URL, slug or numeric/profile ID

No output schema declared.

No examples provided.

enrich_school ~47

Get a school or university from a LinkedIn school URL, slug or numeric ID. 1 credit if found.

NameTypeReqDescription
identifierstringyesLinkedIn URL, slug or numeric/profile ID

No output schema declared.

No examples provided.

get_balance ~17

Show the account's remaining credits and plan.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_lookup ~36

Fetch the result of an earlier lookup by its id (use it when a person lookup is still pending).

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

search_people ~149

Find people by criteria; returns up to 10 LinkedIn slugs per page (enrich them with enrich_person). Filters (all optional, combined with AND): country ["US"], city ["Paris"], title {"any": ["ceo", "head of"]}, company [slug or id], company_size {"min", "max"}, past_company, school, industry_id, company_industry_id, career_years {"min", "max"}, tenure_years {"min", "max"}. Pass next_cursor to get the next page. 1 credit per non-empty page.

NameTypeReqDescription
cursorstring–next_cursor from the previous page
filtersobjectyesAt least one criterion

No output schema declared.

No examples provided.

Install

How do I install the EnrichGrid MCP server?

EnrichGrid is a hosted endpoint at https://enrichgrid.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 · enrichgrid.com

# add to Claude Code
claude mcp add --transport http com-enrichgrid-enrichgrid 'https://enrichgrid.com/mcp'
Common questions

What is the EnrichGrid MCP server?

EnrichGrid is an MCP server listed in the public MCP registry as com.enrichgrid/enrichgrid. LinkedIn person, company and school data plus people search for AI agents. Pay per found profile. This page covers its hosted endpoint (https://enrichgrid.com/mcp).

Is the EnrichGrid MCP server safe to use?

EnrichGrid scores 82 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 EnrichGrid MCP server expose?

EnrichGrid exposes 6 tools: enrich_person, enrich_company, enrich_school, search_people, get_lookup, get_balance. Their descriptions and schemas cost roughly 375 tokens of context every time the server is loaded.

Does the EnrichGrid MCP server require authentication?

Yes. EnrichGrid 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 EnrichGrid MCP server still maintained?

EnrichGrid is still listed as active in the MCP registry. We last reached this channel on 21 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 EnrichGrid MCP server?

VerifyMCP ran 13 checks on EnrichGrid, 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.