Name: Aidenix
Author: aidenix

Aidenix MCP

B2B people and company data: search, your own list, team tools, email checks, lead fit and drafts.

Tool-list grade A Remote · Streamable HTTP API key 18 tools v1.0.1

No reviews yet by aidenix The publisher’s own endpoint — this marketplace is not in the path

93/100

tool-list score

tools declared

remote

at its publisher

—

calls last 7d

What it does

B2B people and company data: search, your own list, team tools, email checks, lead fit and drafts.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --transport http aidenix-mcp https://mcp.aidenix.com/mcp --header 'Authorization: Bearer ${AUTHORIZATION}'

# 2 — ask your agent for something these tools do
#   get_account_context, list_icp_profiles, analyze_contact and 15 more

It needs AUTHORIZATION (Bearer <your Aidenix API token> — get one free at aidenix.com): this sends it in the Authorization header from your environment, so export it first — its endpoint answers 401 without it.

Aidenix costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

aidenix2 servers

2 categories

All 2 servers

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Installation

Where are you running it?

Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.

Claude Codedeclared by this listing

This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it. Claude Code reads AUTHORIZATION (Bearer <your Aidenix API token> — get one free at aidenix.com) from your environment each time it connects and sends it in the Authorization header — its endpoint answers 401 without it — so the key stays out of its config: export it in your shell profile (macOS, Linux), or run setx AUTHORIZATION … and open a new terminal (Windows).

claude mcp add --scope user --transport http aidenix-mcp https://mcp.aidenix.com/mcp --header 'Authorization: Bearer ${AUTHORIZATION}'

Reconnect, or start a new session, and the tools appear in the model’s tool list.

Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add — but its publisher asks for a key of their own on every call.

What it asks of you

It reaches a system of yours, so it needs your own credential rather than the publisher’s: Authorization header — Bearer <your Aidenix API token> — get one free at aidenix.com. You set it in your own client’s config, on your machine — this marketplace never holds it.

What it writes

One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.

What you approve

18 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

Return the authenticated Aidenix account plan, quota, and selected ICP, using the profile website as its human-readable label.

No parameter schema on file.

List ICP profiles by website and product description, including which website is selected.

No parameter schema on file.

Return a complete user-facing single-contact business-fit analysis and outreach drafts. When presenting a completed result, hide technical metadata and use human-readable headings while preserving every user-facing content field.

Parameter	Type	Required	Notes
contact	string	yes	—
icp_profile_id		no	—

Poll one business-fit analysis job and return the complete user-facing result when finished; hide technical metadata and use human-readable headings while preserving every user-facing content field.

Parameter	Type	Required	Notes
job_id	string	yes	—

Submit up to 500 contacts for a named batch business-fit analysis.

Parameter	Type	Required	Notes
contacts	array	yes	—
icp_profile_id		no	—
name		no	—

List batch analyses by name with readable status and progress.

Parameter	Type	Required	Notes
limit	integer	no	—
status		no	—
cursor		no	—

Get readable batch progress and optionally one page of results.

Parameter	Type	Required	Notes
job_id	string	yes	—
include_results	boolean	no	—
result_limit	integer	no	—
cursor		no	—

Create a short-lived CSV or JSON export link for a completed batch.

Parameter	Type	Required	Notes
job_id	string	yes	—
file_format	string	yes	—

Decide whether an email address is worth contacting, before drafting anything. Answers two independent questions: does the mailbox accept mail, and is the person still there. Catches what email verifiers miss — someone who left the company, a renamed domain, a historic address — because a live mailbox at a stale address still bounces the deal, not the message. Costs one request of the user's quota

Parameter	Type	Required	Notes
email	string	yes	Email address to assess before contacting it.
deliverability	boolean	no	Add the SMTP layer (does the mailbox accept mail). Slow. Blind on catch-all domains, where the person layer decides instead.
enrich	boolean	no	Add the dossier: address age, breach exposure, domain reputation, digital footprint, and a company card for the domain. Slow.

Assess a whole list of addresses in one call, before spending analysis on any of them. Same two questions as email_intel — does the mailbox accept mail, is the person still there — answered per address, and returned as a split by recommended action so you can drop the dead ones and keep the rest. Up to 50 addresses per call, or 10 when deliverability or enrich is on, because those layers are slow;

Parameter	Type	Required	Notes
emails	array	yes	Email addresses to assess in one call.
deliverability	boolean	no	Add the SMTP layer to every address. Much slower — the list is capped at 10 when this is on.
enrich	boolean	no	Add the dossier to every address. Much slower — the list is capped at 10 when this is on.

Build the seller's ICP profile by reading their own website: what they sell, the value proposition, which roles and industries they sell to, the pain points, proof points and tone of voice. The new profile becomes the active one, so every later score and every generated email is weighted by it — confirm with the user before running it on a website they have not named. Use it to onboard a new accou

Parameter	Type	Required	Notes
website	string	yes	Website of the company you sell FOR — your own product site, not the prospect's. Its copy becomes the ICP every later score is weighted by.

Profile a company and its current moment before working its people. Given a domain or name, returns firmographics + revenue, team makeup, hiring velocity from careers (which catches layoffs a static card misses), activity signals (funding, hiring focus, product, partnerships, attrition), geo footprint, a growth / reorg / stealth / stable verdict with outreach timing, and a teaser of which organiza

Parameter	Type	Required	Notes
company	string	yes	Company domain (e.g. 'stripe.com') or name. Returns an account-level signal profile: firmographics + revenue, team makeup, hiring velocity from careers (catches layoffs), activity signals (funding/hir
relationships	boolean	no	When true, expands the attention teaser into the full map of who the team collectively follows from public employee activity (likes/comments/shares): organizations they follow most (competitors / vend
enrich	boolean	no	Only meaningful together with relationships. Adds an LLM judgment layer over the map: the real opinion-leaders influencing the buyer, what the attention pattern reveals about priorities, concrete warm

Admin-only: the upstream refuses this tool for customer accounts, so do not offer it as an option — company_signals covers the account and analyze_contact covers the person. Get the people of a company and the addresses to reach them. Given a domain, LinkedIn slug or name, returns the team by name — role, grade, seniority, country, LinkedIn — and the work addresses the sources actually hold, ranke

Parameter	Type	Required	Notes
company	string	yes	Company domain (e.g. 'lemlist.com'), LinkedIn company URL/slug, or name. Returns the team by name with every address the sources actually hold — work, shared inbox and private — each labelled with wha
roles		no	Comma-separated role filter — the people who answer cold email: founder, ceo, cto, cpo, cxo, product, growth, sales. Omit to get the whole team ranked.
top	integer	no	How many people to return by name (default 25). The metrics always describe the whole team behind those rows, so a small top is not a small answer.
contacts	boolean	no	Set to false to skip the contact directories — faster, when you mostly need who works there and in what roles. Addresses carried by the profile snapshots themselves still come back.

Find companies that fit — by industry, size, country, revenue, website tech, the tools their team uses inside, hiring, funding and what they are researching now — without people. Returns one row per company: name, domain, LinkedIn page, industry, size, country, revenue range, funding, website tech stack, intent topics, the company's own public emails, and why it matched. team_uses sees internal to

Parameter	Type	Required	Notes
filters	object	yes	Filters, combined with AND; values inside one list combine with OR. At least one is required. industries ['Software Development'], company_size_min / company_size_max (employees), company_countries ['
limit	integer	no	Companies per page, 1-100. Each company returned costs one request.
cursor		no	next_cursor from the previous page, to continue the same search.

Find people who fit — by role, company and timing — with their contacts. Returns one row per person: name, title, seniority, department, company and its website, LinkedIn, location, the work email at the CURRENT employer, all known work emails, personal emails and phones from professional sources, months in role against their usual tenure, and why they matched. Beyond title and firmographics it fi

Parameter	Type	Required	Notes
filters	object	yes	Filters, combined with AND; values inside one list combine with OR. At least one is required. Who: titles ['vp sales'], levels ['c-level','vp','director','head','manager'], departments ['Sales','Marke
limit	integer	no	People per page, 1-100. Each person returned costs one request.
cursor		no	next_cursor from the previous page, to continue the same search.
only_with_contacts	boolean	no	Skip people without any email or phone.

Who a person is and what is going on with them. Given an email, LinkedIn URL, or slug, returns their role, grade and current company; the career trajectory from dates (months in the seat, whether they grew inside, their usual tenure); what they publish themselves and the subjects they raise; whose content they read; what they said about themselves (looking for work / hiring / milestone); and a ver

Parameter	Type	Required	Notes
person	string	yes	Email, LinkedIn profile URL or slug. Returns who the person is and what is going on with them: role, grade and company; career trajectory from dates (how long in the seat, whether they grew inside); w

Record a person in this account's opt-out list when they ask not to be contacted. Takes an email, phone or LinkedIn profile and detects which it is. Repeating a contact is safe — the second call reports it was already there instead of adding it twice. The list is enforced: contact analysis refuses an excluded contact, and people lists leave them out. Costs no quota — recording a request not to be

Parameter	Type	Required	Notes
contact	string	yes	Email, phone or LinkedIn profile of the person to record in the opt-out list. The kind is detected from the value itself.

Take a contact off this account's opt-out list — for a record added by mistake, or a person who asked to be contacted again. Only a record this account created can be lifted: the list is shared, so one account must not undo an exclusion another was asked for. Reports whether the record was lifted, was never there, or belongs to another account.

Parameter	Type	Required	Notes
contact	string	yes	Email, phone or LinkedIn profile to take off this account's opt-out list. Only a record this account created can be lifted.

Free

$0 forever

Every tool — any call limit is its publisher’s, not ours
No card, and mcprush charges nothing for it
Runs at its publisher’s own address — this marketplace is not in the path
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install Aidenix or to call it, at any volume.

ATool-list grade · score 93 / 100

Release 1.0.1 · scanned 5 Nov 2026

Graded from the tools this server lists, not from its source code.

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score93

Findings0 threat · 1 capability

Capabilitymoderate

Coveragemanifest

Verificationnot in this report

Surface digest2fb2bbe69135666021ea0d588a1ed9ea03bfc9c3ee06a393961edc58847781a5

Score vectorthreat 100 → client 93

Term	Level	What it prices	Points
capability-exposure	moderate	capability blast radius (moderate) — client exposure if the model is manipulated	−3
coverage-honesty	manifest	inspection depth (manifest) — how much of the target the scan could see	−4

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.

Tool surfaceread

Implementation sourcenot available

Package metadatanot available

Live transportnot available

The implementation source was not read — this reflects the declared tool metadata only.

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.

Tool	Capability tags	Why the tag was assigned
get_account_context	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
list_icp_profiles	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
analyze_contact	external-sink	external-sink: declares readOnlyHint: false, openWorldHint: true
get_analysis	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
analyze_contacts	external-sink	external-sink: declares readOnlyHint: false, openWorldHint: true
list_batches	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
get_batch	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
export_batch	external-sink	external-sink: declares readOnlyHint: false, openWorldHint: true
email_intel	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
email_intel_bulk	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
build_icp_profile	external-sink	external-sink: declares readOnlyHint: false, openWorldHint: true
company_signals	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
company_people	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
company_search	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
person_search	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
person_signals	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
add_opt_out	external-sink	external-sink: declares readOnlyHint: false, openWorldHint: true
remove_opt_out	external-sink	external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

flow-1

Untrusted input can drive an external action even though no sensitive source is exposed.

Supply chain and provenance

Integrityfirst-seen

Surface digest2fb2bbe691356660

Scanned2026-11-05

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.