AgentData
REMOTE · MCP.AGENTDATA.RUN · SCANNED SEP 28
Free company data for AI agents: profiles, tech stacks, contact details and people. No sign-in.
Available components
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1719 tokens (~286/item across 6 items; 6 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the AgentData MCP server?
AgentData is a hosted endpoint at https://mcp.agentdata.run/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 · mcp.agentdata.run
claude mcp add --transport http run-agentdata-agentdata 'https://mcp.agentdata.run/mcp'
{
"mcpServers": {
"run-agentdata-agentdata": {
"url": "https://mcp.agentdata.run/mcp"
}
}
} {
"servers": {
"run-agentdata-agentdata": {
"type": "http",
"url": "https://mcp.agentdata.run/mcp"
}
}
} [mcp_servers.run-agentdata-agentdata] url = "https://mcp.agentdata.run/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"run-agentdata-agentdata": {
"type": "remote",
"url": "https://mcp.agentdata.run/mcp",
"enabled": true
}
}
} openclaw mcp add run-agentdata-agentdata --url 'https://mcp.agentdata.run/mcp' --transport streamable-http
mcp_servers:
run-agentdata-agentdata:
url: "https://mcp.agentdata.run/mcp" {
"McpServers": {
"run-agentdata-agentdata": {
"Transport": "http",
"Url": "https://mcp.agentdata.run/mcp"
}
}
} assistant mcp add run-agentdata-agentdata -t streamable-http -u 'https://mcp.agentdata.run/mcp'
{
"mcpServers": {
"run-agentdata-agentdata": {
"type": "http",
"url": "https://mcp.agentdata.run/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 69
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 28 Sept 2026 · Probed https://mcp.agentdata.run/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.agentdata.run | CN=YE1,O=Let's Encrypt,C=US | 12 Aug 2026 | 10 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 64b5a3b476ef119eac9e03a235959e22392 |
| SANs: mcp.agentdata.run | ||||||
| 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 mcp.agentdata.run. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| run. | present | 37315 | 8 | Verified |
| agentdata.run. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.agentdata.run/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.agentdata.run/mcp | HTTPS enforced | 301 | https://mcp.agentdata.run/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 →
check_usage Plan and usage ~51
Use this before a large task to see how much of today's allowance is left: requests in the current 5-hour window, distinct companies today and, with an API key, contact reveals. Free and not counted.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
find_people Find people ~278
Use this when the user wants people at a company or in a role: names, job titles, seniority, department and LinkedIn URLs found on company team, about and author pages. Filter by company domain, name, title, seniority, department, sector or B2B/B2C. Without an API key it returns what the public people directory shows to a visitor who is not signed in: the first 20 matches, with the last 5 withheld, and no email addresses. Narrow the filters (for example a domain plus a title) to get the right people into that first page.
| Name | Type | Req | Description |
|---|---|---|---|
| b2b_b2c | string | – | b2b, b2c or both |
| department | string | – | – |
| domain | string | – | Only people at this company domain, e.g. stripe.com |
| has_email | boolean | – | Only people with an email address found (the address itself needs an API key) |
| has_linkedin | boolean | – | Only people with a LinkedIn URL |
| q | string | – | Name search |
| sector | string | – | Industry sector, exact label from the list |
| seniority | string | – | founder, executive, senior, mid or junior |
| title | string | – | Title contains, e.g. 'CTO', 'Head of Sales' |
No output schema declared.
No examples provided.
get_signals Switch signals ~284
Use this when the user asks which companies recently started, stopped or switched using a technology, for example companies that left Intercom or adopted HubSpot: set moved_from or moved_to. Also covers growth and hiring changes. Newest first. Changes are recorded as each site is re-crawled, so an empty result means none recorded yet, not that none happened. Works without an API key; no contact reveals.
| Name | Type | Req | Description |
|---|---|---|---|
| b2b_b2c | string | – | b2b, b2c or both |
| days | integer | – | Only signals detected in the last N days |
| limit | integer | – | Results per page, default 20 |
| moved_from | string | – | Technology the company dropped, e.g. 'Zendesk' |
| moved_to | string | – | Technology the company adopted, e.g. 'HubSpot' |
| offset | integer | – | – |
| sector | string | – | Industry sector, exact label from the list |
| size | string | – | Estimate, not headcount: a band by how many people and addresses we found on the company's own website: micro (1-5), small (6-20), medium (21-60), large (61+). Large companies often publish few, so d… |
| type | string | – | Signal type; omit for all technology signals |
No output schema declared.
No examples provided.
get_technologies Technologies and who uses them ~203
Use this when the user asks which companies use a particular technology (for example Intercom, Zendesk, HubSpot, Shopify, Stripe), or which technologies are most used. With a slug: companies detected using that technology, 20 per page. company_count is every company detected using it; listed_count is how many the list can page through, so stop at page ceil(listed_count / 20). Without a slug: the technology index, most-used first, with company counts (default 100, up to 1,000). Slugs are lower-case with hyphens, e.g. intercom, hubspot, google-analytics, shopify. Works without an API key; no contact reveals.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Index size when no slug is given, default 100 |
| page | integer | – | Page of companies when a slug is given |
| slug | string | – | Technology slug, e.g. intercom |
No output schema declared.
No examples provided.
lookup_company Look up a company ~283
Use this when the user asks about one specific company and you know its website domain, for example to research an account before a call: what it does, sector and business model, headquarters where known, the tools and technologies it runs (each with how it was detected and when it was first and last seen), and web signals (pricing page, free trial, API docs, careers). Without an API key it returns everything the public company page shows to a visitor who is not signed in: company facts (employees, funding stage, founded, headquarters, sales motion, tech sophistication), the email format (for example {first}.{last}@domain), general inboxes such as info@ and sales@, address and phone where listed, how many email addresses and people were found, the top people's titles, seniority and LinkedIn URLs (not names), recent activity, recent tool changes and similar companies. Personal email addresses and names need an API key; for names at a company use find_people with its domain. A domain not profiled yet is crawled on request: the reply says when to retry, usually within a few minutes, and nothing is charged. Do not use it to find a company by name; use search_companies to get the domain first.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Bare domain, e.g. stripe.com (no https://, no path) |
No output schema declared.
No examples provided.
search_companies Search companies ~335
Use this to find a company by name or part of its domain (query), or to build a list of companies by sector, business model, B2B or B2C, technology used or headquarters country. Returns up to 20 company summaries per page, with how many email addresses were found for each. Use lookup_company for one company's full record, and get_technologies to page through every company using one tool. Works without an API key; no contact reveals.
| Name | Type | Req | Description |
|---|---|---|---|
| b2b | string | – | b2b, b2c or both |
| country | string | – | Headquarters country, ISO-2 code such as US or GB |
| model | string | – | Business model |
| page | integer | – | Page number, 20 companies per page |
| query | string | – | Company name or domain fragment, e.g. 'notion' or 'stripe.com'. Used on its own; filters below are ignored when set. |
| sector | string | – | Industry sector, exact label from the list |
| size | string | – | Estimate, not headcount: a band by how many people and addresses we found on the company's own website: micro (1-5), small (6-20), medium (21-60), large (61+). Large companies often publish few, so d… |
| tech | string | – | Technology name as detected, e.g. 'Intercom', 'HubSpot', 'Shopify' |
| vertical | string | – | Vertical inside the sector, free text as stored, e.g. 'B2B SaaS' |
No output schema declared.
No examples provided.
What is the AgentData MCP server?
AgentData is an MCP server listed in the public MCP registry as run.agentdata/agentdata. Free company data for AI agents: profiles, tech stacks, contact details and people. No sign-in. This page covers its hosted endpoint (https://mcp.agentdata.run/mcp).
Is the AgentData MCP server safe to use?
AgentData scores 69 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 AgentData MCP server expose?
AgentData exposes 6 tools: lookup_company, search_companies, find_people, get_technologies, get_signals, check_usage. Their descriptions and schemas cost roughly 1,434 tokens of context every time the server is loaded.
Does the AgentData MCP server require authentication?
No. We connected to AgentData without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AgentData MCP server still maintained?
AgentData is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.