Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Supero

REMOTE · API.SUPERO.DEV · 2 COMPONENTS

Multi-tenant backend your coding agent configures over MCP: auth, RBAC, data, workflows, deploy.

0 this week 89 Trust /100

Last scanned (22 hours ago)

Scores higher than 96% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CI/CD and DevOps

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability77
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 12928 tokens (~179/item across 72 items; 70 tools + 2 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 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 72 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 19 Nov 26 0
    • New tool “build_production_status” functional
  • 18 Nov 26 0
    • Server version: 2.0.2 → 2.1.0 functional
  • 17 Nov 26 0
    • Tool “apikey_get_scope” rewrote its description, which is the text the model reads security
    • Tool “build_audit” rewrote its description, which is the text the model reads security
    • Tool “build_bind_data_source” rewrote its description, which is the text the model reads security
    • Tool “build_configure_services” rewrote its description, which is the text the model reads security
    • Tool “build_connect_data_source” rewrote its description, which is the text the model reads security
    • Tool “build_create_project” rewrote its description, which is the text the model reads security
    • Tool “build_discover_source” rewrote its description, which is the text the model reads security
    • Tool “build_doctor” rewrote its description, which is the text the model reads security
    • Tool “build_e2e_test” rewrote its description, which is the text the model reads security
    • Tool “build_e2e_test_status” rewrote its description, which is the text the model reads security
    • Tool “build_get_bundle” rewrote its description, which is the text the model reads security
    • Tool “build_get_examples” rewrote its description, which is the text the model reads security
    • Tool “build_get_project” rewrote its description, which is the text the model reads security
    • Tool “build_get_service_contract” rewrote its description, which is the text the model reads security
    • Tool “build_go_live” rewrote its description, which is the text the model reads security
    • Tool “build_go_production” rewrote its description, which is the text the model reads security
    • Tool “build_import_services” rewrote its description, which is the text the model reads security
    • Tool “build_list_bound_schemas” rewrote its description, which is the text the model reads security
    • Tool “build_list_capabilities” rewrote its description, which is the text the model reads security
    • Tool “build_list_data_sources” rewrote its description, which is the text the model reads security
    • Tool “connector_run” rewrote its description, which is the text the model reads security
    • Tool “connector_status” rewrote its description, which is the text the model reads security
    • Tool “connector_test” rewrote its description, which is the text the model reads security
    • Tool “connector_test_config” rewrote its description, which is the text the model reads security
    • Tool “crud_create” rewrote its description, which is the text the model reads security
    • Tool “crud_delete” rewrote its description, which is the text the model reads security
    • Tool “crud_get” rewrote its description, which is the text the model reads security
    • Tool “crud_search” rewrote its description, which is the text the model reads security
    • Tool “crud_update” rewrote its description, which is the text the model reads security
    • Tool “project_link_schemas” rewrote its description, which is the text the model reads security
    • Tool “rbac_check_permission” rewrote its description, which is the text the model reads security
    • Tool “rbac_get_my_access” rewrote its description, which is the text the model reads security
    • Tool “schema_delete” rewrote its description, which is the text the model reads security
    • Tool “schema_get” rewrote its description, which is the text the model reads security
    • Tool “schema_list” rewrote its description, which is the text the model reads security
    • Tool “schema_list_project” rewrote its description, which is the text the model reads security
    • Tool “schema_save” rewrote its description, which is the text the model reads security
    • Tool “schema_update” rewrote its description, which is the text the model reads security
    • Tool “schema_validate” rewrote its description, which is the text the model reads security
    • Tool “sdk_download” rewrote its description, which is the text the model reads security
    • Tool “sdk_generate” rewrote its description, which is the text the model reads security
    • Tool “sdk_list” rewrote its description, which is the text the model reads security
    • Tool “sdk_status” rewrote its description, which is the text the model reads security
    • Tool “build_list_projects” rewrote its description, which is the text the model reads security
    • Tool “build_logs” rewrote its description, which is the text the model reads security
    • Tool “build_plan” rewrote its description, which is the text the model reads security
    • Tool “build_publish” rewrote its description, which is the text the model reads security
    • Tool “build_recommend_integrations” rewrote its description, which is the text the model reads security
    • Tool “build_replace_project” rewrote its description, which is the text the model reads security
    • Tool “build_report” rewrote its description, which is the text the model reads security
    • Tool “build_run_data_source” rewrote its description, which is the text the model reads security
    • Tool “build_set_project_mode” rewrote its description, which is the text the model reads security
    • Tool “build_smoke_test” rewrote its description, which is the text the model reads security
    • Tool “build_stage_bundle” rewrote its description, which is the text the model reads security
    • Tool “build_teardown” rewrote its description, which is the text the model reads security
    • Tool “build_update_project” rewrote its description, which is the text the model reads security
    • Tool “build_validate” rewrote its description, which is the text the model reads security
    • Tool “build_verify” rewrote its description, which is the text the model reads security
    • Tool “build_whoami” rewrote its description, which is the text the model reads security
    • Tool “connector_cancel” rewrote its description, which is the text the model reads security
    • Tool “connector_disable” rewrote its description, which is the text the model reads security
    • Tool “connector_discover” rewrote its description, which is the text the model reads security
    • Tool “connector_discover_results” rewrote its description, which is the text the model reads security
    • Tool “connector_discover_status” rewrote its description, which is the text the model reads security
    • Tool “connector_enable” rewrote its description, which is the text the model reads security
    • Tool “connector_plugins” rewrote its description, which is the text the model reads security
    • Tool “build_deploy” rewrote its description, which is the text the model reads security
    • Tool “build_deploy_status” rewrote its description, which is the text the model reads security
    • Tool “build_get_skills” rewrote its description, which is the text the model reads security
    • Schema quality: 11412 → 12606 ▼ functional
    • Schema quality: 165 → 186 ▼ functional
    • Schema quality: excellent → good functional
    • New prompt “supero_build_app” functional
    • New prompt “supero_connect_database” functional
    • New resource “Supero build guide” functional
    • New tool “build_report” functional
    • “build_audit” added an optional parameter “base_version” cosmetic
    • “build_audit” added an optional parameter “patch” cosmetic
    • “build_doctor” added an optional parameter “base_version” cosmetic
    • “build_doctor” added an optional parameter “patch” cosmetic
    • “build_get_skills” added an optional parameter “topic” cosmetic
    • “build_plan” added an optional parameter “project_uuid” cosmetic
    • “build_plan” added an optional parameter “ui_polish” cosmetic
    • “build_publish” added an optional parameter “base_version” cosmetic
    • “build_publish” added an optional parameter “patch” cosmetic
    • “build_validate” added an optional parameter “base_version” cosmetic
    • “build_validate” added an optional parameter “patch” cosmetic
    • “build_verify” added an optional parameter “cleanup_only” cosmetic
    • “build_verify” added an optional parameter “event_tests” cosmetic
    • “build_verify” added an optional parameter “run_id” cosmetic
    • “build_get_skills” reworded the description of “doc” cosmetic
  • 15 Nov 26 0
    • Tool “build_go_production” rewrote its description, which is the text the model reads security
    • Tool “build_logs” rewrote its description, which is the text the model reads security
    • “build_logs” added an optional parameter “error” cosmetic
    • “build_create_project” reworded the description of “description” cosmetic
    • “build_create_project” reworded the description of “is_multi_tenant” cosmetic
    • “build_create_project” reworded the description of “requirements” cosmetic
  • 14 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 2.0.1 → 2.0.2 functional
  • 13 Nov 26 0
    • Tool “build_get_examples” rewrote its description, which is the text the model reads security
  • 11 Nov 26 0
    • “build_recommend_integrations” added an optional parameter “google_signin” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 10 Nov 26 0
    • Tool “build_plan” rewrote its description, which is the text the model reads security
    • “build_create_project” added an optional parameter “is_multi_tenant” cosmetic
    • “build_plan” added an optional parameter “answers” cosmetic
    • “build_plan” added an optional parameter “audience” cosmetic
    • “build_plan” added an optional parameter “choices” cosmetic
    • “build_plan” added an optional parameter “confirmed” cosmetic
    • “build_plan” added an optional parameter “currency” cosmetic
    • “build_plan” added an optional parameter “exclude” cosmetic
    • “build_plan” added an optional parameter “governance” cosmetic
    • “build_plan” added an optional parameter “interactive” cosmetic
    • “build_plan” added an optional parameter “locale” cosmetic
    • “build_plan” added an optional parameter “payments” cosmetic
    • “build_plan” added an optional parameter “prd” cosmetic
    • “build_plan” added an optional parameter “signup_mode” cosmetic
    • “build_plan” added an optional parameter “tenancy” cosmetic
Diagnostics

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 21 Nov 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 24 Oct 2026 22 Jan 2027 ECDSA 256 ECDSA-SHA256 db4605aac2bbed970eee37ee04e64817
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. DS published 60074 8 Verified
supero.dev. No DS 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
MCP tools · 70 exposed · ~12,710 tokens

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 →

Tool Tokens
connector_test_config ~42

Tests a connector configuration before it is saved (input: config). Returns whether the source is reachable with it.

NameTypeReqDescription
configobjectyesConnector config to test.

No output schema declared.

No examples provided.

crud_create ~200

Creates an object in the current domain. Inputs: object_type, name, optional parent_type, parent_fq_name, data, tenant. Returns the created object. schema_list shows the types and their fields.

NameTypeReqDescription
dataobject–Object fields as key-value pairs
namestringyesObject name (required for most types)
object_typestringyesThe object type to create (e.g. 'customer', 'appointment', 'project')
parent_fq_namearray–Parent FQ name path (e.g. ['cine-corp', 'car-service'])
parent_typestring–Parent type if applicable (e.g. 'project' for tenant, 'domain' for project)
tenantstring–Optional tenant name to create the object under (multi-tenant apps: seed a specific named tenant's data). Omit for single-tenant apps — the session/API-key tenant is used.

No output schema declared.

No examples provided.

crud_delete ~95

Deletes an object from the current domain. Inputs: object_type, uuid, optional tenant. The deletion is permanent.

NameTypeReqDescription
object_typestringyesThe object type
tenantstring–Optional tenant name context for this delete (multi-tenant apps). Omit for single-tenant apps — the session/API-key tenant is used. Deletes address the record by UUID.
uuidstringyesObject UUID to delete

No output schema declared.

No examples provided.

crud_get ~57

Returns one object by UUID from the current domain. Inputs: object_type, uuid.

NameTypeReqDescription
object_typestringyesThe object type (e.g. 'customer', 'project', 'tenant')
uuidstringyesObject UUID

No output schema declared.

No examples provided.

crud_search ~367

Searches or lists objects of one type in the current domain. Inputs: object_type, optional filters / filter, sort, limit, offset, tenant. Returns matching rows. System types: project, tenant, user_account, api_key, connector, audit_log, schema_registry, client_sdk, connector_execution, connector_plugin; domain types vary per domain (schema_list shows them).

NameTypeReqDescription
filterobject–Optional boolean filter tree for and/or/not logic, e.g. {"op": "or", "conditions": [{"status": "open"}, {"amount": {"gt": 500}}]}. Use `filters` for simple AND-ed conditions.
filtersobject–Filter criteria keyed by field. A plain value is equality (e.g. {"status": "active"}); an object of operators compares (e.g. {"amount": {"gte": 10, "lt": 100}}). Operators: eq, ne, gt, gte, lt, lte,…
limitinteger–Max results (default: 100, max 1000)
object_typestringyesThe object type to search (e.g. 'customer', 'project', 'tenant', 'connector')
offsetinteger–Skip N results for pagination
sort––Optional sort: a field name ('amount', or '-amount' for descending), {"field": "amount", "order": "desc"}, or a list of those.
tenantstring–Optional tenant name to scope the search to (multi-tenant apps: verify a specific named tenant's data). Omit for single-tenant apps — the session/API-key tenant is used.

No output schema declared.

No examples provided.

crud_update ~110

Updates fields of an existing object in the current domain. Inputs: object_type, uuid, data, optional tenant. Returns the updated object.

NameTypeReqDescription
dataobjectyesFields to update
object_typestringyesThe object type
tenantstring–Optional tenant name context for this update (multi-tenant apps). Omit for single-tenant apps — the session/API-key tenant is used. Updates address the record by UUID.
uuidstringyesObject UUID to update

No output schema declared.

No examples provided.

project_link_schemas ~102

Links existing schemas to a project, by schema_uuids or schema_names. Input: project_uuid. Returns the linked schemas.

NameTypeReqDescription
project_uuidstringyesUUID of the project to link schemas to.
schema_namesarray–List of schema names to link (resolved to UUIDs). Use 'namespace:name' when a name exists in several namespaces.
schema_uuidsarray–List of schema registry UUIDs to link.

No output schema declared.

No examples provided.

rbac_check_permission ~55

Checks whether the current user has a given permission (input: permission). Returns true or false with the reason.

NameTypeReqDescription
permissionstringyesPermission to check (e.g. 'schema:manage', 'data:write').

No output schema declared.

No examples provided.

rbac_get_my_access ~24

Returns the current user's role, permissions and scope. No inputs.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

schema_delete ~63

Deletes a schema from the domain by schema_uuid (optional force_delete). Records of that type stop being reachable through it.

NameTypeReqDescription
force_deleteboolean–Force delete even with dependencies (default: false).
schema_uuidstringyesUUID of the schema to delete.

No output schema declared.

No examples provided.

schema_get ~60

Returns a schema's full definition by schema_uuid, including all attributes and metadata (include_content for the content).

NameTypeReqDescription
include_contentboolean–Include full schema content (default: true).
schema_uuidstringyesUUID of the schema to retrieve.

No output schema declared.

No examples provided.

schema_list ~19

Lists the schemas in the current domain. No inputs.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

schema_list_project ~83

Lists the schemas linked to a project (optional project_uuid, include_content).

NameTypeReqDescription
include_contentboolean–Include full schema content (default: true).
project_uuidstring–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 ~358

Saves schemas into a project, validating them first and linking them to the project. Returns the saved schemas with their UUIDs; skipped schemas carry the platform's reason. Input format: flat schema objects in `schemas` (not wrapped in schema_content); the tool detects the schema type and wraps it. Required fields: name, namespace, parent_type, attributes. namespace is the app's namespace (e.g. 'shop'); the schema is stored as namespace:name. Required attributes carry "mandatory": true. Attribute types: 'string' for text, 'float' for decimal numbers (not 'number'), 'integer' for whole numbers, 'boolean' for true/false. project_uuid defaults to the key's project; a project-scoped key saves only into its own project. A schema skipped for compatibility warnings is applied with force_upload=true. Example: { "schemas": [{ "name": "product", "namespace": "shop", "description": "Product catalog entry", "parent_type": "tenant", "attributes": [ {"name": "title", "type": "string", "mandatory": true}, {"name": "price", "type": "float"}, {"name": "stock", "type": "integer"} ] }] }

NameTypeReqDescription
force_uploadboolean–Apply changes that only have compatibility WARNINGS (default: false). Breaking changes are still refused.
project_uuidstring–Project to save into (defaults to your key's project; required for a domain-admin key).
schemasarrayyesArray of schema definitions to save.
skip_existingboolean–Skip schemas that already exist (default: true).

No output schema declared.

No examples provided.

schema_update ~96

Updates an existing schema definition. Inputs: schema_uuid, schema_content, optional new_version, check_compatibility. Returns the updated schema.

NameTypeReqDescription
check_compatibilityboolean–Check compatibility with existing data (default: true).
new_versionstring–Optional new version string.
schema_contentobjectyesNew schema content (full schema definition).
schema_uuidstringyesUUID of the schema to update.

No output schema declared.

No examples provided.

schema_validate ~56

Validates schemas without saving them: conflicts with existing schemas, circular dependencies, reserved names and parent_type. Input: schemas. Returns errors and warnings. Useful before schema_save.

NameTypeReqDescription
schemasarrayyesArray of schema definitions to validate.

No output schema declared.

No examples provided.

sdk_download ~50

Returns a download URL for an SDK (inputs: sdk_uuid, optional artifact).

NameTypeReqDescription
artifactstring–Artifact type (default: 'wheel').
sdk_uuidstringyesUUID of the SDK.

No output schema declared.

No examples provided.

sdk_generate ~84

Generates client SDKs for the domain's schemas (optional languages, force_rebuild, include_docs). Returns a request_id for sdk_status.

NameTypeReqDescription
force_rebuildboolean–Force rebuild (default: false).
include_docsboolean–Include docs (default: true).
languagesarray–Languages to generate (default: ['python', 'javascript']).

No output schema declared.

No examples provided.

sdk_list ~47

Lists the SDKs available for the current domain (optional language, limit).

NameTypeReqDescription
languagestring–Filter by language.
limitinteger–Max results (default: 50).

No output schema declared.

No examples provided.

sdk_status ~35

Returns the status of an SDK generation request (input: request_id).

NameTypeReqDescription
request_idstringyesRequest ID from sdk_generate.

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http supero-platform-supero 'https://api.supero.dev/mcp/v1/messages'
Common questions

What is the Supero MCP server?

Supero is an MCP server listed in the public MCP registry as io.github.supero-platform/supero. Multi-tenant backend your coding agent configures over MCP: auth, RBAC, data, workflows, deploy. This page covers its hosted endpoint (https://api.supero.dev/mcp/v1/messages).

Is the Supero MCP server safe to use?

Supero scores 89 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 70 tools: build_get_skills, build_get_examples, build_plan, build_get_service_contract, build_whoami, and 65 more. Their descriptions and schemas cost roughly 12,710 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Supero MCP server?

VerifyMCP ran 13 checks on Supero, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.