AgentData
by agentdata.run · remote · no sign-in to list tools · v2.2.0 · published by run.agentdata
Free company data for AI agents: profiles, tech stacks, contact details and people. No sign-in.
6 tools: 1 change things and 5 only read.
Scanned Oct 21, 2026
- Deletes or cancels0Claude Code: deny
- Can't be undone0Claude Code: ask
- Changes things1Claude Code: ask: see these tools
- Only reads5Claude Code: allow: see these tools
No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http agentdata https://mcp.agentdata.run/mcpTools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
6 tools
Changes things 1Claude Code: ask
check_usageUse 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Plan and usage
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
Only reads 5Claude Code: allow
find_peopleUse 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.No findings
Why it is in this group
- The name "find_people" says "find": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Find people
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
get_signalsUse 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…No findings
Why it is in this group
- The name "get_signals" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Switch signals
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
get_technologiesUse this when the user asks which companies use a particular technology (for example Intercom, Zendesk, HubSpot, Shopify, Stripe), or which technologies are most used.No findings
Why it is in this group
- The name "get_technologies" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Technologies and who uses them
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
lookup_companyUse 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, h…No findings
Why it is in this group
- The name "lookup_company" says "lookup": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Look up a company
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
search_companiesUse 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.No findings
Why it is in this group
- The name "search_companies" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Search companies
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Install
Pinned to version 2.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http agentdata https://mcp.agentdata.run/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__agentdata__lookup_company",
"mcp__agentdata__search_companies",
"mcp__agentdata__find_people",
"mcp__agentdata__get_technologies",
"mcp__agentdata__get_signals"
],
"ask": [
"mcp__agentdata__check_usage"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as agentdata. Review it before you use it.