Agrus.ai — Enterprise AI Agency MCP server
io.github.phwizard/mcp-agrus-aiphwizardstreamable-httpv0.2.0Scanned
AI consulting agency for regulated industries. Scope a PoC, query compliance, request a proposal.
7 tools: 3 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Agrus.ai — Enterprise AI Agency MCP server can do
The Agrus.ai — Enterprise AI Agency MCP server is published by the GitHub account phwizard. It has 7 tools. It can create or change data (3 tools: scope_poc, request_quote and request_proposal), but cannot delete data. 4 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 20, 2026, version 0.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
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 4Show 4 read-only tools
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.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:09 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.agrus.ai/mcp: tools/list returned 7 tools to an anonymous client, including scope_poc (write), request_quote (write), request_proposal (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
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/mcpclaude mcp add --transport http agrus-ai https://mcp.agrus.ai/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as agrus-ai. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.phwizard/mcp-agrus-ai/verify?hash=6309aa1ad13c30d54084502884271673b079f57f5204c3f3de01b7a9986b8a2e" | jq -e '.changed == false'Pinned hash 6309aa1ad13c, from Nov 20, 2026, 07:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.phwizard/mcp-agrus-ai/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.phwizard/mcp-agrus-ai)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:43 UTC.
Agrus.ai — Enterprise AI Agency MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Agrus.ai — Enterprise AI Agency MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Agrus.ai — Enterprise AI Agency MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Agrus.ai — Enterprise AI Agency MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Agrus.ai — Enterprise AI Agency MCP server have?
- 7 tools: 3 write, 4 read. scope_poc, request_quote, request_proposal, list_services, list_verticals, query_compliance_position and get_case_study.
Does the Agrus.ai — Enterprise AI Agency MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Agrus.ai — Enterprise AI Agency MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Agrus.ai — Enterprise AI Agency MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.