Skip to content

Agrus.ai — Enterprise AI Agency

by phwizard · remote · no sign-in to list tools · v0.2.0 · published by GitHub user phwizard

AI consulting agency for regulated industries. Scope a PoC, query compliance, request a proposal.

Changes · 3
CompareRegistry entry

7 tools: 3 change things and 4 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http agrus-ai https://mcp.agrus.ai/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

7 tools

Changes things 3Claude Code: ask
  • request_proposalTriggers a formal Agrus proposal workflow.No findings

    Why it is in this group

    • The name "request_proposal" says "request": a word for a change.
    Description, as the server wrote it
    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 Agrus — not for exploratory scoping.
  • request_quoteReturns a heuristic ballpark price band for the described AI deployment.No findings

    Why it is in this group

    • The name "request_quote" says "request": a word for a change.
    Description, as the server wrote it
    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.
  • scope_pocDrafts a structured Discovery Sprint scope for an AI use case.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.
    Description, as the server wrote it
    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.
Only reads 4Claude Code: allow
  • get_case_studyReturns one or more Agrus case studies (NDA-protected; customer names are kept private, codenames + technology + outcomes are open).No findings

    Why it is in this group

    • The name "get_case_study" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • list_servicesLists Agrus's six service pillars with descriptions, deliverables, and price bands.No findings

    Why it is in this group

    • The name "list_services" says "list": a word for reading.
    Description, as the server wrote it
    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.
  • list_verticalsLists Agrus's seven year-one verticals (healthcare, insurance, legal, private equity, family offices, corporate intelligence, pro sports) with compliance pins, sample use cases, an…No findings

    Why it is in this group

    • The name "list_verticals" says "list": a word for reading.
    Description, as the server wrote it
    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.
  • query_compliance_positionReturns 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.No findings

    Why it is in this group

    • The name "query_compliance_position" says "query": a word for reading.
    Description, as the server wrote it
    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.

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 0.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http agrus-ai https://mcp.agrus.ai/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__agrus-ai__list_services",
      "mcp__agrus-ai__list_verticals",
      "mcp__agrus-ai__query_compliance_position",
      "mcp__agrus-ai__get_case_study"
    ],
    "ask": [
      "mcp__agrus-ai__scope_poc",
      "mcp__agrus-ai__request_quote",
      "mcp__agrus-ai__request_proposal"
    ],
    "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 agrus-ai. Review it before you use it.