aci-mcp

by DevadiptaDas

Overview Schema Related Servers Score Discussions

Python

Local

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v0.1.0
Disambiguation4/5
Tools orgainize into three recognizable domains — personal memory (recall/remember/ingest/validate), shared skills (find/save/outcome), and collaboration (post/team_activity) — with clear read/write pairs. Two pairs (recall vs validate and remember vs ingest) could cause initial misselection, but their descriptions give distinct triggers: search-by-meaning vs claim-checking, and single-fact vs folder ingestion.
Naming Consistency4/5
All tools share the aci_ prefix in snake_case, with most following a verb (recall, remember, ingest, validate) or verb+object pattern (find_skills, save_skill, post_work). aci_skill_outcome and aci_team_activity break the verb convention with noun-noun names, a minor deviation in an otherwise predictable scheme.
Tool Count5/5
Nine tools cover three cohesive subdomains — memory (4), skills (3), and shared work log (2) — with each tool serving a distinct purpose and no apparent redundancy. This sits comfortably in the well-scoped 3-15 range for a server of this breadth.
Completeness4/5
Memory has write (remember/ingest), read (recall), and verification (validate) but no explicit forget/delete tool; agents can work around this via re-storing corrections. Skills have a full find/save/feedback lifecycle, and the work log has both write and read sides, so core workflows are well covered with only a minor gap.
Average 4.3/5 across 9 of 9 tools scored.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 2 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI is passing
This repository is licensed under Apache 2.0.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of explaining side effects. It discloses that saving publishes to a shared library, re-saving corroborates, and improved versions supersede older ones only after proving reliable. It does not cover failure modes or exact visibility semantics, but the core behavior is transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Three focused sentences: the first establishes the core purpose, the second covers versioning behavior, and the third gives selection guidance. There is slight redundancy between 'reusable' and 'reuse it,' but overall the description is compact and front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a publish tool with no annotations and no output schema, the description covers the action, the type of content, side effects, and when to use it. It omits operational specifics such as how success is returned or how 'proves reliable' is determined, but nothing essential is missing for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3. The description adds a little semantic color by clarifying that the 'body' is a procedure, how-to, or prompt and that skills are declarative, but it does not meaningfully enrich the meaning of name, intent, tags, or author beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the action ('Publish'), the object ('a reusable, DECLARATIVE skill'), and the destination ('shared library so other AIs can find and reuse it'). It also explicitly contrasts the resource with runnable code, which distinguishes this tool from other skill-related siblings like find, validate, and remember.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives practical selection guidance: save skills you worked out that others would reuse, and exclude runnable code from this tool. It also explains re-saving behavior and supersession. It does not explicitly name sibling alternatives, but the context is strong enough for an agent to know when this tool applies.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral burden. It discloses that the tool searches, returns skills ranked by confidence, and includes steps and author, which is meaningful beyond the schema. It does not discuss empty-result behavior or potential side effects, but 'Search ... Returns' implies a read operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two purposeful sentences with no filler. It front-loads the core action, gives an example, and then states the output and a preference rule, so every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a two-parameter tool with no output schema, the description covers the trigger, use case, output content, and ranking behavior. It could be more complete with explicit sibling routing or empty-result behavior, but it is sufficient for an agent to select and invoke the tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already documents both parameters with 100% coverage, so the baseline is 3. The description reinforces 'intent' with a natural-language example and explains the purpose of the search, but it adds little beyond the schema for 'k'.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific action ('Search the shared SKILL library by intent'), a concrete use case, and a worked example ('how to draft an arbitration notice'). It also distinguishes the tool's output by 'ranked by EARNED confidence (ψ)', making its role clear.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly says to use this tool 'before doing a task' and to prefer a high-confidence existing skill over improvising, which gives clear when-to-use context. It does not name alternative sibling tools or state when not to use it, so it stops short of a perfect score.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the behavioral disclosure burden. It volunteers useful details: processing is incremental, on-device, and cheap to re-run. It does not mention permissions, reversibility, or potential long initial indexing time, but the disclosed behavior is genuinely informative.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is four sentences with no filler; each sentence contributes distinct value: primary action, usage triggers, behavioral characteristics, and a parameter constraint. It is compact and front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter ingest tool with no annotations and no output schema, the description covers purpose, when to use it, key behavior, and parameter guidance. It omits output/return behavior, but that is a minor gap for an ingest operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description adds a helpful clarification that the path must be an absolute FOLDER path and not a single file, but full_resync is left entirely to the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb (Index), a clear resource (a FOLDER on the user's machine into their ACI memory), and the outcome (documents become recallable in future sessions). This clearly differentiates it from retrieval-focused siblings like aci_recall.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives concrete trigger phrases ('remember everything in this folder', 'index my Cases folder', 'learn my documents') that tell an agent when to use it. It does not explicitly discuss when not to use it or name alternative tools, so it is slightly short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the burden—and it does well by disclosing that the log is shared, visible to the user and other AI agents, and that every ACI agent reads and writes the same log. It doesn't cover auth, retention, or error behavior, but the core write/visibility semantics are transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Three tight sentences: first states the action, second gives the usage context, third clarifies shared visibility. No filler or redundant restatement of the tool name or schema.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple write-only logging tool, the description covers purpose, trigger condition, content examples, and visibility. It omits response/error behavior, but that is not essential for an agent to select and invoke this tool correctly, especially with fully documented parameters.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema coverage is 100%, and the schema already defines 'note', 'agent', and 'project' meaningfully. The description reinforces what belongs in 'note' (decisions, findings, completed steps) but adds no format or constraint details beyond the schema, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Record') and a clear resource ('shared work log' / 'ACI commons'), and states the outcome: other AIs and the user can see it. This distinguishes it from the memory/skill-oriented sibling tools by anchoring it to shared project work logging.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly says when to use it: 'when collaborating with other agents on the same project,' and gives examples of what to log (decisions, findings, completed steps). It does not name alternatives or exclusion conditions, but the collaboration context is clear enough for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral burden. It goes beyond the schema by disclosing the side effects: 'Success raises its confidence; failure lowers it' and frames the tool as the library's self-curation mechanism. It doesn't mention return format or auth, but the key behavioral impact is clearly disclosed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, front-loaded with the core purpose, then the behavioral effect, then the timing. Every sentence earns its place with no filler or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter reporting tool, the description covers purpose, timing, and behavioral consequences. It lacks an explicit return-value statement, but that is not essential for invoking the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the schema already fully describes both parameters. The description adds the conceptual meaning of the 'success' boolean (raising or lowering confidence), but does not add format, constraints, or examples beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Report') with a clear resource ('whether a skill from the library actually WORKED') and explains its role in the library's self-curation. The purpose is unmistakable and is distinct from siblings like aci_save_skill or aci_find_skills.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives explicit timing context: 'Call it after acting on a skill from aci_find_skills.' This is clear contextual guidance, though it does not explicitly list exclusions or compare itself to alternative tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral burden. 'See' and 'work log' strongly imply a read-only, non-mutating operation, and it discloses the data source ('the user's ACI commons'). It could be more explicit about side-effect-freedom, but the read-only intent is clear.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two compact sentences, front-loaded with the core function and followed by the usage trigger. Every phrase adds value; there is no fluff or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with one optional parameter and no output schema, the description covers what it does, where the data comes from, and when to call it. It does not describe the exact return shape, but 'log' and the catch-up purpose give enough context for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The only parameter 'project' is fully described in the input schema as 'filter to one project (optional),' so the description adds no new parameter-level meaning. With 100% schema coverage, the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'See what every AI (and the user) has done on a shared project — the cross-agent work log.' This clearly differentiates it from siblings like aci_remember or aci_find_skills, which deal with memory and skills rather than team activity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicit guidance is given: 'Call this when you start collaborating to catch up on what other agents already did, so you don't duplicate their work.' This is a clear trigger context, though it does not mention when not to use it or name alternative tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden of behavioral disclosure. It makes clear this is a non-destructive search, describes ranking behavior, mentions time-travel semantics for as_of, and instructs the agent to disclose ACI-VPU grounding. It does not cover failure modes or permissions, but for a recall/search tool the key behavior is well disclosed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences front-load the core purpose, then add the always-call rule, the as_of behavior, and the grounding instruction. There is no filler; every clause adds actionable information for the agent.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 3-parameter search tool with no output schema, the description is nearly complete: it states what is searched, how results are ranked, when to invoke, and how to report usage. It does not describe the return shape or edge cases, which would be useful, but an agent can select and invoke the tool correctly based on what is provided.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already documents all 3 parameters at 100% coverage, so the baseline is 3. The description adds meaningful value by framing as_of as 'time-travel' with concrete use cases and clarifying that query is a natural-language meaning search. It does not elaborate on k, but the schema already handles that adequately.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific operation ('Search the user's ACI cognition memory by meaning'), defines the resource scope ('files, web pages, notes and facts from past sessions'), and specifies ranking semantics ('semantic similarity, TRUST and recency'). This clearly distinguishes it from sibling write/lookup tools like aci_remember or aci_ingest.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It provides explicit when-to-use guidance: 'ALWAYS call this before answering anything that could depend on the user's own data, documents, decisions or history', and explains why it is preferable to guessing or asking. It also gives a concrete scenario for the as_of parameter, but it does not name alternatives or exclusion conditions, so it falls just short of a full 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It honestly discloses the key side effect: the memory is durable and shared across all future sessions and apps. It does not mention overwrite, deletion, or limits, but the core persistence behavior is clearly conveyed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no filler. The main action and durability scope are front-loaded in the first sentence, and the usage boundary is in the second. Every clause earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple 2-parameter tool with no annotations and no output schema, the description supplies enough context for an agent to invoke it correctly: what to store, why it matters, and what not to store. Minor gaps like duplicate handling or memory limits are not critical for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description adds extra meaning for the content parameter by defining what qualifies as a stable fact ('about themselves, their work, or decisions'), going slightly beyond the schema's generic 'the fact to remember'.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Store') and resource ('the user's ACI memory'), and clarifies the scope: durable facts available to every future session and other ACI-connected apps. This clearly distinguishes it from sibling tools like aci_recall and aci_save_skill.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly says to use this tool for stable facts about the user, their work, or decisions, and explicitly excludes ephemeral chit-chat. It does not name alternative sibling tools, but the use-case guidance is clear enough to route an agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description carries the full burden, and it does so well. It discloses the trust-weighted rule ('a grounded fact overrides a lie repeated many times'), the return shape (supports/contradicts, confidence score, explanation), and how to handle flagged results. This goes well beyond the schema and the tool name.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three sentences with no filler: first the core function, then the return value, then the usage directive. Each sentence earns its place and the most important information is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter validation tool with no output schema, the description is complete. It covers what the tool does, how it behaves, what it returns, when to use it, and what to do after a flag. Nothing essential for invoking it correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single parameter 'statement' has a schema description ('the statement to check') that covers it 100%, so the schema already communicates the core meaning. The description reinforces that the statement is a claim that may conflict with stored knowledge, but it adds no new format, constraints, or examples beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description starts with a specific verb ('Check') and a clear resource ('the user's ACI memory'), then specifies the purpose: contradictions and confidence. It also conveys the trust-weighted behavior, which distinguishes it from sibling tools like aci_recall or aci_remember without needing to name them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly tells the agent when to call this tool: 'ALWAYS call this before you rely on, or repeat to the user, any claim that could conflict with what they actually know.' It also gives a concrete follow-up action — tell the user the claim was checked or caught via ACI-VPU — so the usage guidance is actionable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![ACI-VPU MCP server](https://glama.ai/mcp/servers/DevadiptaDas/ACI-VPU/badges/card.svg)](https://glama.ai/mcp/servers/DevadiptaDas/ACI-VPU)

Score Badge

Copy to your README.md:

[![ACI-VPU MCP server](https://glama.ai/mcp/servers/DevadiptaDas/ACI-VPU/badges/score.svg)](https://glama.ai/mcp/servers/DevadiptaDas/ACI-VPU)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DevadiptaDas/ACI-VPU'

If you have feedback or need assistance with the MCP directory API, please join our Discord server