Agrus.ai — Enterprise AI Agency
REMOTE · MCP.AGRUS.AI
AI consulting agency for regulated industries. Scope a PoC, query compliance, request a proposal.
Available components
Last scanned (2 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 Nov 2026.
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1183 tokens (~169/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 10 Oct 26 −2
- HSTS header: pass → fail ▼ security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.agrus.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agrus.ai | CN=YE1,O=Let's Encrypt,C=US | 14 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5aa6b5b94a09c52c386f6f17214c5a1023d |
| SANs: *.agrus.ai, agrus.ai | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.agrus.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| agrus.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.agrus.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.agrus.ai/mcp | HTTPS enforced | 301 | https://mcp.agrus.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_case_study ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | – | Specific case-study slug. If omitted, returns all available case studies (filtered by vertical if provided). |
| vertical | string | – | Filter case studies by vertical. Ignored if slug is provided. |
No output schema declared.
No examples provided.
list_services ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| vertical | string | – | Filter services by vertical applicability. Currently all services apply to all verticals. |
No output schema declared.
No examples provided.
list_verticals ~65
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
query_compliance_position ~195
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.
| Name | Type | Req | Description |
|---|---|---|---|
| data_types | array | – | Optional list of data types the AI would touch (e.g. ['PHI', 'PII', 'claims data', 'underwriting decisions']). |
| 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'). |
No output schema declared.
No examples provided.
request_proposal ~314
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company / organization name. |
| compliance_constraints | array | – | Regulatory regimes the deployment must satisfy. |
| 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'. |
| persona_context | string | – | 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>'). |
| role | string | – | 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. |
| urgency | string | – | How quickly the buyer wants to move. |
| vertical | string | yes | Which Agrus vertical the use case sits in. |
No output schema declared.
No examples provided.
request_quote ~173
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.
| Name | Type | Req | Description |
|---|---|---|---|
| compliance_constraints | array | – | Regulatory regimes the deployment must satisfy. Drives the compliance overlay on the quote. |
| 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. |
| urgency | string | – | Free-form timeline indicator. |
| vertical | string | yes | Which Agrus vertical the use case sits in. |
No output schema declared.
No examples provided.
scope_poc ~249
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.
| Name | Type | Req | Description |
|---|---|---|---|
| compliance_constraints | array | – | Regulatory regimes the deployment must satisfy. Drives compliance overlay in the scope. |
| data_types | array | – | Data the AI would touch (e.g. ['PHI', 'patient demographics', 'EHR notes']). |
| target_outcomes | array | – | What success looks like (e.g. ['reduce adjuster review time by 50%', 'production pilot with 3 clinicians by Q3']). |
| timeline_hint | string | – | Free-form timeline (e.g. 'exploring', 'this quarter', 'production by Q4', 'this is blocking board commitment'). |
| 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. |
No output schema declared.
No examples provided.
How do I install the Agrus.ai — Enterprise AI Agency MCP server?
Agrus.ai — Enterprise AI Agency is a hosted endpoint at https://mcp.agrus.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.agrus.ai
claude mcp add --transport http phwizard-mcp-agrus-ai 'https://mcp.agrus.ai/mcp'
What is the Agrus.ai — Enterprise AI Agency MCP server?
Agrus.ai — Enterprise AI Agency is an MCP server listed in the public MCP registry as io.github.phwizard/mcp-agrus-ai. AI consulting agency for regulated industries. Scope a PoC, query compliance, request a proposal. This page covers its hosted endpoint (https://mcp.agrus.ai/mcp).
Is the Agrus.ai — Enterprise AI Agency MCP server safe to use?
Agrus.ai — Enterprise AI Agency scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Agrus.ai — Enterprise AI Agency MCP server expose?
Agrus.ai — Enterprise AI Agency exposes 7 tools: list_services, list_verticals, query_compliance_position, get_case_study, scope_poc, and 2 more. Their descriptions and schemas cost roughly 1,183 tokens of context every time the server is loaded.
Does the Agrus.ai — Enterprise AI Agency MCP server require authentication?
No. We connected to Agrus.ai — Enterprise AI Agency without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agrus.ai — Enterprise AI Agency MCP server still maintained?
Agrus.ai — Enterprise AI Agency is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.