SubmitraX
REMOTE · MCP.SUBMITRAX.COM
Form backend for static sites: create forms, manage submissions, webhooks and exports.
Available components
Last scanned (15 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Workflow Automation
Recent critical change
Authorization (18 Nov 2026). See the changelog before you install this server.
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_form). See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 2634 tokens (~46/item across 57 items; 57 tools + 0 resources), lean.Pass
- 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 10 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 57 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
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 →
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.
- 18 Nov 26 +45
- Authorization: unverified → fail ▼ critical
- HSTS header: unverified → fail ▼ security
- DNSSEC: unverified → fail ▼ security
- HTTPS: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 17 Nov 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 16 Nov 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 15 Nov 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 13 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Authorization: fail → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 11 Nov 26 +1
- DNSSEC: fail → unverified ▼ security
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 8 Nov 26 +1
- Stability: 0.97 → pass security
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://mcp.submitrax.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.submitrax.com | CN=YE1,O=Let's Encrypt,C=US | 21 Nov 2026 | 19 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6508a4efcb8e3cb7a7fcd5fe855164a7c68 |
| SANs: mcp.submitrax.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.submitrax.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| submitrax.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.submitrax.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.submitrax.com/mcp | Inconclusive | 405 |
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 →
update_member_role Update member role ~69
Change a workspace member's role. Requires admin access to the workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| memberId | string | yes | Member ID, as returned by list_workspace_members |
| role | string | yes | New role, e.g. 'admin' or 'member' |
| workspaceId | string | yes | Workspace ID |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Response body returned by the SubmitraX API |
No examples provided.
update_template_admin Update template (admin) ~97
Update a template. Requires super-admin.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | Template HTML content |
| description | string | – | Short description of the template |
| id | string | yes | Template ID |
| is_default | boolean | – | Whether the template is offered to all users by default |
| name | string | – | Template name |
| slug | string | – | URL-friendly identifier for the template |
| type | string | – | Template type |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Response body returned by the SubmitraX API |
No examples provided.
update_user_plan_admin Update user plan (admin) ~49
Set a user's plan ('free' or 'pro') and its associated quota. Requires super-admin.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | User ID |
| plan | string | yes | Plan to assign |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Response body returned by the SubmitraX API |
No examples provided.
update_user_quota_admin Update user quota (admin) ~43
Set a user's submission quota directly. Requires super-admin.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | User ID |
| submission_quota | number | yes | New submission quota |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Response body returned by the SubmitraX API |
No examples provided.
update_user_role_admin Update user admin role ~51
Grant or revoke super-admin status for a user. Requires super-admin.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | User ID |
| is_super_admin | boolean | yes | true to grant super-admin, false to revoke |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Response body returned by the SubmitraX API |
No examples provided.
update_workspace Update workspace ~46
Rename a workspace or change its settings.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Workspace ID |
| name | string | – | New workspace name |
| settings | object | – | Workspace settings to merge |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Response body returned by the SubmitraX API |
No examples provided.
upgrade_user_plan Upgrade user plan ~44
Change the authenticated user's plan (defaults to 'pro' if not specified).
| Name | Type | Req | Description |
|---|---|---|---|
| plan | string | – | Plan to switch to, e.g. 'pro' (default) |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Response body returned by the SubmitraX API |
No examples provided.
How do I install the SubmitraX MCP server?
SubmitraX is a hosted endpoint at https://mcp.submitrax.com/mcp, 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 · mcp.submitrax.com
claude mcp add --transport http com-submitrax-mcp 'https://mcp.submitrax.com/mcp'
What is the SubmitraX MCP server?
SubmitraX is an MCP server listed in the public MCP registry as com.submitrax/mcp. Form backend for static sites: create forms, manage submissions, webhooks and exports. This page covers its hosted endpoint (https://mcp.submitrax.com/mcp).
Is the SubmitraX MCP server safe to use?
SubmitraX scores 75 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 SubmitraX MCP server expose?
SubmitraX exposes 57 tools: set_auth_token, get_auth_status, register, login, login_with_google, and 52 more. Their descriptions and schemas cost roughly 2,634 tokens of context every time the server is loaded.
Does the SubmitraX MCP server require authentication?
No. We connected to SubmitraX without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SubmitraX MCP server still maintained?
SubmitraX 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 SubmitraX MCP server?
VerifyMCP ran 12 checks on SubmitraX, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about SubmitraX: HTTPS. 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.