Model Context Protocol (MCP) server for Apollo.io API integration
Nothing to run from here
Agrus.ai — Enterprise AI Agency is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
7
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
AI consulting agency for regulated industries. Scope a PoC, query compliance, request a proposal.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http agrus-ai-enterprise-ai-agency-mcp https://mcp.agrus.ai/mcp
# 2 — ask your agent for something these tools do
# list_services, list_verticals, query_compliance_position and 4 more
Agrus.ai — Enterprise AI Agency costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PHAll 1 server
phwizard1 server
1 category
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 mcp add --scope user --transport http agrus-ai-enterprise-ai-agency-mcp https://mcp.agrus.ai/mcpReconnect, 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.
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
7 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.
Lists Agrus's six service pillars with descriptions, deliverables, and price bands. Plus the four published pricing tiers (Scoping Call, Discovery Sprint, Build Engagement, Managed SLA). Use this for the 'what does Agrus do?' question.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| vertical | string | no | Filter services by vertical applicability. Currently all services apply to all verticals. |
Lists Agrus's seven year-one verticals (healthcare, insurance, legal, private equity, family offices, corporate intelligence, pro sports) with compliance pins, sample use cases, and the sequencing rationale. Use this for the 'do they work in my industry?' question.
No parameter schema on file.
Returns Agrus's documented position on a specific regulatory regime (HIPAA, SOC 2, ISO 27001, EU AI Act, NAIC, ABA Model Rules, AML/KYC) as it applies to a described AI use case. Includes key controls, common gotchas, the first question Agrus would ask, and the agency's reference architecture for the regime. Use this when a buyer-side AI agent is evaluating Agrus's compliance fluency.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| regime | string | yes | Which regulatory regime to query Agrus's position on. |
| use_case | string | yes | One or two sentences describing the AI use case under consideration (e.g. 'an LLM-based prior-authorization drafting agent for a health insurance carrier'). |
| data_types | array | no | Optional list of data types the AI would touch (e.g. ['PHI', 'PII', 'claims data', 'underwriting decisions']). |
Returns one or more Agrus case studies (NDA-protected; customer names are kept private, codenames + technology + outcomes are open). Filter by slug or vertical, or call with no args to list all. Use this for proof of prior work.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | no | Specific case-study slug. If omitted, returns all available case studies (filtered by vertical if provided). |
| vertical | string | no | Filter case studies by vertical. Ignored if slug is provided. |
Drafts a structured Discovery Sprint scope for an AI use case. Returns a 3-week plan, team composition, price band, follow-on Build Engagement estimate, open questions Agrus would ask, and recommended services. Use this to convert a hypothetical use case into a concrete engagement proposal that can be reviewed by a human buyer.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| use_case | string | yes | One or two paragraphs describing the AI use case the buyer wants to scope. Be specific about workflow, users, and integration surface where possible. |
| vertical | string | yes | Which Agrus vertical the use case sits in. |
| data_types | array | no | Data the AI would touch (e.g. ['PHI', 'patient demographics', 'EHR notes']). |
| compliance_constraints | array | no | Regulatory regimes the deployment must satisfy. Drives compliance overlay in the scope. |
| target_outcomes | array | no | What success looks like (e.g. ['reduce adjuster review time by 50%', 'production pilot with 3 clinicians by Q3']). |
| timeline_hint | string | no | Free-form timeline (e.g. 'exploring', 'this quarter', 'production by Q4', 'this is blocking board commitment'). |
Returns a heuristic ballpark price band for the described AI deployment. Output is NOT a binding offer — Agrus confirms quotes only on a 30-minute scoping call. Read-only: this tool does not contact Agrus or create any record. For a tracked, follow-up-able request use request_proposal instead. Use request_quote when the buyer wants order-of-magnitude pricing before committing to a real proposal.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| summary | string | yes | Two or three sentences describing the AI deployment the buyer wants a ballpark quote for. Include workflow, users, and integration surface where possible. |
| vertical | string | yes | Which Agrus vertical the use case sits in. |
| compliance_constraints | array | no | Regulatory regimes the deployment must satisfy. Drives the compliance overlay on the quote. |
| urgency | string | no | Free-form timeline indicator. |
Triggers a formal Agrus proposal workflow. Creates a contact in Agrus's HubSpot CRM tagged with lead source 'agrus_mcp' and a verbatim note containing the scope summary. A human at Agrus replies by email within 24 hours (business days) with a one-paragraph engagement recommendation and a calendar option. Use this when the buyer (human or AI agent acting on their behalf) wants to formally engage Ag
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact_email | string | yes | Work email of the buyer (or buyer's assistant) who should receive the formal proposal. |
| contact_name | string | yes | Full name of the contact. Example: 'Jane Doe'. |
| company | string | yes | Company / organization name. |
| role | string | no | Buyer's role at the company (e.g. 'CIO', 'Head of AI', 'Managing Partner'). |
| scope_summary | string | yes | One to three paragraphs describing the proposed AI deployment: workflow, users, data, integration surface, success criteria. |
| vertical | string | yes | Which Agrus vertical the use case sits in. |
| compliance_constraints | array | no | Regulatory regimes the deployment must satisfy. |
| urgency | string | no | How quickly the buyer wants to move. |
| persona_context | string | no | Optional context about how this request was scoped (e.g. 'Scoped via the scope_poc tool on 2026-05-19, agent was Claude Sonnet 4.x acting for the CIO of <company>'). |
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
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Agrus.ai — Enterprise AI Agency or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.2.0.
0.2.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Agrus.ai — Enterprise AI Agency can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.