Supero
REMOTE · API.SUPERO.DEV · SCANNED SEP 30
Build multi-tenant apps over MCP. Schemas, CRUD, deploys — access control enforced server-side.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 7502 tokens (~115/item across 65 items; 64 tools + 1 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 Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 87% of tool parameters carry a description.Partial
Tool Safety95
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 4 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "build_deploy_status" implies "deploy" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 66 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the Supero MCP server?
Supero is a hosted endpoint at https://api.supero.dev/mcp/v1/messages, 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 · api.supero.dev
claude mcp add --transport http supero-platform-supero 'https://api.supero.dev/mcp/v1/messages'
{
"mcpServers": {
"supero-platform-supero": {
"url": "https://api.supero.dev/mcp/v1/messages"
}
}
} {
"servers": {
"supero-platform-supero": {
"type": "http",
"url": "https://api.supero.dev/mcp/v1/messages"
}
}
} [mcp_servers.supero-platform-supero] url = "https://api.supero.dev/mcp/v1/messages"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"supero-platform-supero": {
"type": "remote",
"url": "https://api.supero.dev/mcp/v1/messages",
"enabled": true
}
}
} openclaw mcp add supero-platform-supero --url 'https://api.supero.dev/mcp/v1/messages' --transport streamable-http
mcp_servers:
supero-platform-supero:
url: "https://api.supero.dev/mcp/v1/messages" {
"McpServers": {
"supero-platform-supero": {
"Transport": "http",
"Url": "https://api.supero.dev/mcp/v1/messages"
}
}
} assistant mcp add supero-platform-supero -t streamable-http -u 'https://api.supero.dev/mcp/v1/messages'
{
"mcpServers": {
"supero-platform-supero": {
"type": "http",
"url": "https://api.supero.dev/mcp/v1/messages"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +5
- HTTPS: unverified → pass ▲ security
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
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 30 Sept 2026 · Probed https://api.supero.dev/mcp/v1/messages
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=supero.dev | CN=WE1,O=Google Trust Services,C=US | 25 Aug 2026 | 23 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 71652014602d07d113add22c16ee272c |
| SANs: supero.dev, *.supero.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.supero.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| supero.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="Supero MCP"
Bearer realm="Supero MCP"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.supero.dev/mcp/v1/messages | Verified | 200 | |
| http (plaintext) | http://api.supero.dev/mcp/v1/messages | HTTPS enforced | 301 | https://api.supero.dev/mcp/v1/messages |
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 →
project_link_schemas ~77
Link schemas to a project. Accepts schema UUIDs or names.
| Name | Type | Req | Description |
|---|---|---|---|
| project_uuid | string | yes | UUID of the project to link schemas to. |
| schema_names | array | – | List of schema names to link (resolved to UUIDs). |
| schema_uuids | array | – | List of schema registry UUIDs to link. |
No output schema declared.
No examples provided.
rbac_check_permission ~43
Check if the current user has a specific permission.
| Name | Type | Req | Description |
|---|---|---|---|
| permission | string | yes | Permission to check (e.g. 'schema:manage', 'data:write'). |
No output schema declared.
No examples provided.
rbac_get_my_access ~21
Get current user's role, permissions, and scope.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
schema_delete ~50
Delete a schema from the domain. Use with caution.
| Name | Type | Req | Description |
|---|---|---|---|
| force_delete | boolean | – | Force delete even with dependencies (default: false). |
| schema_uuid | string | yes | UUID of the schema to delete. |
No output schema declared.
No examples provided.
schema_get ~59
Get full details of a specific schema by UUID. Returns the complete schema definition including all attributes and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| include_content | boolean | – | Include full schema content (default: true). |
| schema_uuid | string | yes | UUID of the schema to retrieve. |
No output schema declared.
No examples provided.
schema_list ~17
List all existing schemas in the current domain.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
schema_list_project ~76
List schemas linked to the current project.
| Name | Type | Req | Description |
|---|---|---|---|
| include_content | boolean | – | Include full schema content (default: true). |
| project_uuid | string | – | Project to list schemas for. Optional; defaults to the key's project when resolvable (pass the project_uuid from build_whoami/build_list_projects under an API key). |
No output schema declared.
No examples provided.
schema_save ~279
Save/upload schemas to the domain. Schemas are validated before saving. Returns list of successfully saved schemas with their UUIDs. IMPORTANT: Pass FLAT schema objects directly — do NOT wrap in schema_content. The tool handles schema_type detection and wrapping automatically. Required fields: name, parent_type, prefix, plural_name, attributes, description. Supported attribute types: 'string' for text, 'float' for decimal numbers (NOT 'number'), 'integer' for whole numbers, 'boolean' for true/false. Optionally pass project_uuid to auto-link saved schemas to a project. Example: { "schemas": [{ "name": "product", "description": "Product catalog entry", "parent_type": "tenant", "prefix": "prd", "plural_name": "products", "attributes": [ {"name": "title", "type": "string", "required": true}, {"name": "price", "type": "float"}, {"name": "stock", "type": "integer"} ] }] }
| Name | Type | Req | Description |
|---|---|---|---|
| project_uuid | string | – | Optional project UUID to auto-link saved schemas to. |
| schemas | array | yes | Array of schema definitions to save. |
| skip_existing | boolean | – | Skip schemas that already exist (default: true). |
No output schema declared.
No examples provided.
schema_update ~74
Update an existing schema definition.
| Name | Type | Req | Description |
|---|---|---|---|
| check_compatibility | boolean | – | Check compatibility with existing data (default: true). |
| new_version | string | – | Optional new version string. |
| schema_content | object | yes | New schema content (full schema definition). |
| schema_uuid | string | yes | UUID of the schema to update. |
No output schema declared.
No examples provided.
schema_validate ~49
Validate schemas before saving. Checks for conflicts with existing schemas, circular dependencies, reserved names, and parent_type correctness. Always validate before saving!
| Name | Type | Req | Description |
|---|---|---|---|
| schemas | array | yes | Array of schema definitions to validate. |
No output schema declared.
No examples provided.
sdk_download ~41
Get download URL for an SDK.
| Name | Type | Req | Description |
|---|---|---|---|
| artifact | string | – | Artifact type (default: 'wheel'). |
| sdk_uuid | string | yes | UUID of the SDK. |
No output schema declared.
No examples provided.
sdk_generate ~66
Generate client SDKs for the domain's schemas.
| Name | Type | Req | Description |
|---|---|---|---|
| force_rebuild | boolean | – | Force rebuild (default: false). |
| include_docs | boolean | – | Include docs (default: true). |
| languages | array | – | Languages to generate (default: ['python', 'javascript']). |
No output schema declared.
No examples provided.
sdk_list ~41
List available SDKs for the current domain.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Filter by language. |
| limit | integer | – | Max results (default: 50). |
No output schema declared.
No examples provided.
sdk_status ~27
Check SDK generation request status.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | Request ID from sdk_generate. |
No output schema declared.
No examples provided.
What is the Supero MCP server?
Supero is an MCP server listed in the public MCP registry as io.github.supero-platform/supero. Build multi-tenant apps over MCP. Schemas, CRUD, deploys, access control enforced server-side. This page covers its hosted endpoint (https://api.supero.dev/mcp/v1/messages).
Is the Supero MCP server safe to use?
Supero scores 85 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 Supero MCP server expose?
Supero exposes 64 tools: crud_search, crud_get, crud_create, crud_update, crud_delete, and 59 more. Their descriptions and schemas cost roughly 7,379 tokens of context every time the server is loaded.
Does the Supero MCP server require authentication?
Yes. Supero asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Supero MCP server still maintained?
Supero is still listed as active in the MCP registry. We last reached this channel on 30 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.