Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
66 changes: 66 additions & 0 deletions mcp-registry/servers/0nmcp.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,66 @@
{
"name": "0nmcp",
"display_name": "0nMCP — Universal AI API Orchestrator",
"description": "564 tools across 26 services in 13 categories. Stripe, Slack, Discord, SendGrid, GitHub, Shopify, Gmail, Google Sheets, Jira, Zendesk, and more. Natural language AI orchestration with Vault encryption, Business Deed transfer, and Application Engine.",
"repository": {
"type": "git",
"url": "https://github.com/0nork/0nMCP"
},
"homepage": "https://0nmcp.com",
"author": {
"name": "0nORK"
},
"license": "MIT",
"categories": [
"Dev Tools",
"Automation"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Use an allowed category enum value

The category "Automation" is not one of the allowed values in mcp-registry/schema/server-schema.json (the enum lists values like "Dev Tools", "AI Systems", etc.), so this manifest will fail the schema validation job configured in .github/workflows/test.yml for pull requests. As written, this blocks the registry entry from passing CI until the category is changed to a schema-supported value.

Useful? React with 👍 / 👎.

],
Comment on lines +14 to +17

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

1. Invalid category value 🐞 Bug ✓ Correctness

The manifest includes category "Automation", which is not in the schema’s allowed categories enum.
This will fail the CI schema validation job that checks all mcp-registry/servers/*.json files.
Agent Prompt
### Issue description
`mcp-registry/servers/0nmcp.json` uses a category value ("Automation") that is not allowed by the registry schema enum, causing CI schema validation to fail.

### Issue Context
The CI workflow validates all manifests against `mcp-registry/schema/server-schema.json`, which defines an enum list for `categories`.

### Fix Focus Areas
- mcp-registry/servers/0nmcp.json[14-17]
- mcp-registry/schema/server-schema.json[70-90]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

"tags": [
"MCP",
"AI",
"orchestration",
"automation",
"api",
"stripe",
"slack",
"crm",
"vault",
"encryption"
],
"installations": {
"npm": {
"type": "npm",
"command": "npx",
"args": [
"-y",
"0nmcp"
],
"env": {
"ANTHROPIC_API_KEY": {
"description": "Optional — enables AI-powered multi-step planning",
"required": false
}
Comment on lines +39 to +42

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Encode installation env values as strings

Under installations.*.env, the schema requires each environment variable value to be a string, but ANTHROPIC_API_KEY is defined as an object (description/required). This violates mcp-registry/schema/server-schema.json and will cause the pull-request schema validation workflow (.github/workflows/test.yml) to fail for this manifest.

Useful? React with 👍 / 👎.

},
Comment on lines +38 to +43

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

2. Installations.env type mismatch 🐞 Bug ⛯ Reliability

installations.npm.env is defined as an object-of-objects with description/required, but the
schema and runtime code expect env to be a simple map of string-to-string. This will fail CI
schema validation and can crash mcpm when constructing FullServerConfig.
Agent Prompt
### Issue description
The manifest encodes env var metadata inside `installations.npm.env`, but the registry schema requires `env` values to be strings and `mcpm` runtime expects `env: Dict[str,str]`. This breaks CI validation and may crash installs.

### Issue Context
Other manifests store env var metadata under top-level `arguments` and keep `installations.*.env` as a string-to-string mapping (typically using `${VAR}` templates).

### Fix Focus Areas
- mcp-registry/servers/0nmcp.json[30-47]
- mcp-registry/schema/server-schema.json[214-295]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

"recommended": true,
"description": "Run the 0nMCP server using Node.js npx"
}
},
"examples": [
{
"title": "Multi-Service Orchestration",
"description": "Invoice a customer and notify a Slack channel",
"prompt": "Invoice john@acme.com for $500 and notify #sales on Slack when it's sent"
},
{
"title": "Service Connection",
"description": "Connect to a service with your API key",
"prompt": "Connect to Stripe with key sk_live_xxx"
},
Comment on lines +55 to +58

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Do not model live secret sharing in example prompts.

Line 57 uses sk_live_xxx, which encourages entering production-style keys in chat contexts. Replace with test-key wording and an explicit “never share live keys” cue.

Proposed diff
     {
       "title": "Service Connection",
-      "description": "Connect to a service with your API key",
-      "prompt": "Connect to Stripe with key sk_live_xxx"
+      "description": "Connect to a service using a test API key (never share live keys)",
+      "prompt": "Connect to Stripe using test key sk_test_xxx"
     },
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"title": "Service Connection",
"description": "Connect to a service with your API key",
"prompt": "Connect to Stripe with key sk_live_xxx"
},
"title": "Service Connection",
"description": "Connect to a service using a test API key (never share live keys)",
"prompt": "Connect to Stripe using test key sk_test_xxx"
},
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@mcp-registry/servers/0nmcp.json` around lines 55 - 58, Update the example
prompt under the "Service Connection" object: replace the production-style
example key string "sk_live_xxx" with a test-key example such as "sk_test_xxx"
and append an explicit safety cue like "—never share live/production keys" (or
similar) in the "prompt" value to discourage sharing real secrets; locate the
"prompt" field within the object titled "Service Connection" and modify its
string accordingly.

{
"title": "CRM Management",
"description": "Search and manage CRM contacts",
"prompt": "Look up sarah@example.com in my CRM and send her a follow-up email"
}
],
"is_official": true
}
Loading