Developer · Local MCP server
Ai Supply
Search, install, publish & review security-scanned AI capabilities from ai-supply.store.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.ai-supply-store/ai-supply- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-06-15
- Updated
- 2026-06-15
- Publisher
- ai-supply-store (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/ai-supply-store) · how
- Website
- ai-supply.store
- Repository
- github.com/ai-supply-store/ai-supply-plugin
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | ai-supply-mcp | 1.0.0 | stdio |
How to connect Ai Supply
Ai Supply runs locally from a Node.js package published to the npm registry: ai-supply-mcp version 1.0.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y ai-supply-mcp@1.0.0. It reads these environment variables: AIM_API_KEY (required, secret) and AIM_BASE_URL; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"ai-supply": {
"command": "npx",
"args": [
"-y",
"ai-supply-mcp@1.0.0"
],
"env": {
"AIM_API_KEY": "<secret>",
"AIM_BASE_URL": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| AI ScannerScan codebases for LLM/AI SDK usage, exposed API tokens, and hardcoded secrets. | Local · stdio |
| AI Site ScorerCheck website AI-readiness: Schema.org, llms.txt, E-E-A-T, robots.txt. Works in Cursor & Claude. | Remote · HTTPLive check: ✓ handshake |
| AI Skill StoreAgent-first skill marketplace with USK open standard for Claude, Cursor, Gemini, Codex CLI. | Remote · HTTPLive check: ✗ no handshake |
| AI Success StoryFirst-person AI war-stories from coding sessions, searchable via MCP for prior-art consultation. | Remote · HTTPLive check: ✗ no handshake |
| AI UsageReports real token usage and cost from Claude Code and OpenCode data. Nothing leaves your machine. | Local · stdio |
| Ai ValidationIndependent AI code validation: test bias, edge cases, coverage gaps. | Local · stdio |
| AI Visibility Audit - Can AI crawlers read and cite your site?One-call audit: robots.txt AI-bot rules, llms.txt, JSON-LD, meta tags, sitemap. Score plus fixes. | Remote · HTTPLive check: ✓ handshake |
| AI Workbench MCPRead-only MCP server for reusable AI prompts and assistant blueprints. | Local · stdio |