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.

Croft

REMOTE · MCP.ONCROFT.NET · SCANNED OCT 2

Deploy and host the apps your AI assistant builds — a real server, database, and shareable URL.

Available components

0 this week 39 Trust /100
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 Security97
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
  • Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.

Install

How do I install the Croft MCP server?

Croft is a hosted endpoint at https://mcp.oncroft.net/, 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.oncroft.net

# add to Claude Code
claude mcp add --transport http net-oncroft-croft 'https://mcp.oncroft.net/'
// .cursor/mcp.json
{
  "mcpServers": {
    "net-oncroft-croft": {
      "url": "https://mcp.oncroft.net/"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "net-oncroft-croft": {
      "type": "http",
      "url": "https://mcp.oncroft.net/"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.net-oncroft-croft]
url = "https://mcp.oncroft.net/"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "net-oncroft-croft": {
      "type": "remote",
      "url": "https://mcp.oncroft.net/",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add net-oncroft-croft --url 'https://mcp.oncroft.net/' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  net-oncroft-croft:
    url: "https://mcp.oncroft.net/"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "net-oncroft-croft": {
      "Transport": "http",
      "Url": "https://mcp.oncroft.net/"
    }
  }
}
# add to Vellum
assistant mcp add net-oncroft-croft -t streamable-http -u 'https://mcp.oncroft.net/'
// mcp.json
{
  "mcpServers": {
    "net-oncroft-croft": {
      "type": "http",
      "url": "https://mcp.oncroft.net/"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 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
  • 25 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
  • 2 Sept 26 0
    • Authorization: partial → pass ▲ security
  • 26 Aug 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
  • 19 Aug 26 0
    • Endpoint reachability: reachable → behind authorisation ▼ security
    • Stability: 0.37 → unverified ▼ security
    • Transport: pass → unverified ▼ security
    • Authorization: The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 18 Aug 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 17 Aug 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 16 Aug 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
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 2 Oct 2026 · Probed https://mcp.oncroft.net

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=oncroft.net CN=WE1,O=Google Trust Services,C=US 21 Sept 2026 20 Dec 2026 ECDSA 256 ECDSA-SHA256 4e1648b1dbf2cff91387c1844d3e6f58
SANs: oncroft.net, *.oncroft.net
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 mcp.oncroft.net. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
net. present 37331 13 Verified
oncroft.net. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On connection
HTTP status 401

WWW-Authenticate challenge Bearer resource_metadata="https://mcp.oncroft.net/.well-known/oauth-protected-resource", scope="workspace"

Bearer resource_metadata="https://mcp.oncroft.net/.well-known/oauth-protected-resource", scope="workspace"
Header Value
strict-transport-security max-age=63072000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
www-authenticate Bearer resource_metadata="https://mcp.oncroft.net/.well-known/oauth-protected-resource", scope="workspace"

Protected resource metadata

Document https://mcp.oncroft.net/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://mcp.oncroft.net
Authorisation server https://app.oncroft.net

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.oncroft.net Auth required 401
http (plaintext) http://mcp.oncroft.net HTTPS enforced 308 https://mcp.oncroft.net/
MCP tools · 26 exposed · ~1,900 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
create_app ~57

Provisions an empty app on this workspace: a git repo, subdomain, port, and golden-path scaffold files. It contains no feature implementation and is not yet live.

NameTypeReqDescription
descriptionstring––
namestringyes–
NameTypeReqDescription
appstring––
conventionsstring––
filesarray––
liveboolean––
urlstring––

No examples provided.

delete_app ~83

Permanently deletes an app: removes its containers, data, and source code from the server, then deletes the app record. Irreversible. Does not affect other apps or the server. Deletes only when confirm is true.

NameTypeReqDescription
appstringyes–
confirmbooleanyesMust be true for the deletion to proceed; otherwise the call is a no-op.
NameTypeReqDescription
appstring––
confirmation_requiredboolean––
deletedstring––
okboolean––

No examples provided.

deploy ~76

Commits, builds (Nixpacks), and deploys the app. Returns a deploy job id; the build runs in the background and its deploy_state moves through queued and running before it ends in succeeded or failed. The app is live only once the deploy has succeeded.

NameTypeReqDescription
appstringyes–
messagestring––
NameTypeReqDescription
appstring––
deploy_jobinteger––
liveboolean––
statusstring––

No examples provided.

describe_connector ~49

Returns a connector's full manifest — base URL, auth style, and the named operations (method, path, params) an app can call. Never returns the credential.

NameTypeReqDescription
namestringyes–
NameTypeReqDescription
auth_stylestring––
base_urlstring––
descriptionstring––
enabledboolean––
has_credentialboolean––
kindstring––
namestring––
operationsarray––
statusstring––

No examples provided.

get_app ~30

Get an app's file manifest, recent releases, and secret key names.

NameTypeReqDescription
namestringyes–
NameTypeReqDescription
filesarray––
namestring––
public_pathsarray––
releasesarray––
schedulesarray––
secret_keysarray––
sharedboolean––
statusstring––
urlstring––

No examples provided.

get_platform_conventions ~26

Return the Croft golden-path rules that every app on this workspace must follow.

Input schema present but exposes no named parameters.

NameTypeReqDescription
conventionsstring––

No examples provided.

grant_access ~31

Grant an existing user access to an app.

NameTypeReqDescription
appstringyes–
emailstringyes–
NameTypeReqDescription
appstring––
emailstring––
okboolean––

No examples provided.

grant_connector ~131

Gives one of your apps access to a connector. The app can then call the connector's operations. Note: this lets the app's code, and everyone the app is shared with, use the connector's credential. A connector an admin has marked admins-only can only be granted by an admin. Some connectors require admin approval: when a creator grants one of those, the grant is created as 'requested' and an owner/admin must approve it (they're emailed) before the app can use it — owners/admins granting it are approved automatically.

NameTypeReqDescription
appstringyes–
connectorstringyes–
NameTypeReqDescription
appstring––
connectorstring––
statestring––

No examples provided.

invite_user ~122

Invite someone by email, set their workspace role, and grant app access. role is member (use apps), creator (can build their own apps), or admin. apps is 'all' or a list of app names.

NameTypeReqDescription
appsstring|array–Which apps to grant access to: "all" for every app, or a list of app names.
emailstringyesEmail address of the person to invite.
rolestring–Workspace role: member (uses shared apps), creator (builds their own apps), or admin.
NameTypeReqDescription
apps–––
invitedstring––

No examples provided.

list_apps ~24

List the apps in this workspace with their URLs, status, and last release.

Input schema present but exposes no named parameters.

NameTypeReqDescription
app_limitinteger––
appsarray––
apps_remaininginteger––

No examples provided.

list_connectors ~51

Lists the workspace's API connectors (external services apps can call without holding the credential) and their state. `active` connectors are usable; `draft` ones still need a workspace admin to add the credential.

Input schema present but exposes no named parameters.

NameTypeReqDescription
connectorsarray––

No examples provided.

list_grants ~29

Lists the connectors an app can reach and each grant's state.

NameTypeReqDescription
appstringyes–
NameTypeReqDescription
appstring––
grantsarray––

No examples provided.

list_secret_keys ~27

List an app's secret key names (never values).

NameTypeReqDescription
appstringyes–
NameTypeReqDescription
keysarray––

No examples provided.

list_users ~21

List the people in this workspace and which apps they can access.

Input schema present but exposes no named parameters.

NameTypeReqDescription
usersarray––

No examples provided.

logs ~34

Recent runtime logs for an app (relayed from its box).

NameTypeReqDescription
appstringyes–
linesinteger––
NameTypeReqDescription
appstring––
healthstring––
logsstring––

No examples provided.

propose_connector ~192

Creates a new API connector as a DRAFT from the vendor's API docs: you supply the base URL, auth style, and an operations manifest. A workspace member (owner, admin, or creator) then opens the panel and adds the credential to activate it — the credential never passes through you. auth_style is bearer|header|query|basic; for header/query also give auth_param (the header/param name).

NameTypeReqDescription
auth_paramstring–Header or query-param name (for header/query auth).
auth_stylestringyes–
base_urlstringyeshttps base URL, e.g. "https://api.stripe.com".
descriptionstring––
namestringyesShort slug, e.g. "stripe".
operationsobjectyesMap of operation name → { method, path, params: [names] }. Path may contain {placeholders}.
NameTypeReqDescription
connectorstring––
operationsarray––
statusstring––

No examples provided.

read_file ~69

Read one file from an app's own git repo on this Croft workspace. No external API — the path is resolved inside the app's repository.

NameTypeReqDescription
appstringyesThe app's name.
pathstringyesRepo-relative file path, e.g. "app/models/user.rb".
NameTypeReqDescription
contentstring––
pathstring––

No examples provided.

request_public_data_access ~112

For an app that has PUBLIC routes: request permission for it to use protected resources (its granted connectors AND other apps' shared data). Public apps are blocked from these by default so a public page can't leak workspace data. If you (the caller) are an owner or admin, this is granted immediately; if you're a creator it creates a request that an owner/admin approves (they're emailed). Call this when building a public app that also needs a connector or shared data.

NameTypeReqDescription
appstringyes–
NameTypeReqDescription
appstring––
public_data_accessboolean––
statestring––

No examples provided.

revoke_access ~31

Revoke a user's access to an app.

NameTypeReqDescription
appstringyes–
emailstringyes–
NameTypeReqDescription
okboolean––

No examples provided.

rollback ~24

Re-deploy the previous release of an app.

NameTypeReqDescription
appstringyes–
NameTypeReqDescription
deploy_jobinteger––
statusstring––

No examples provided.

set_database_sharing ~215

Turns this app's database sharing on or off. Off by default (the database is private). When on, other apps in the same workspace may read AND write this app's SQLite database through Croft's internal broker at http://croft-data:8080/q/<this-app-name> (send {"sql":"…","params":[…]}), and this app is listed to other apps as reusable shared data. By default apps that have PUBLIC routes cannot read this shared data (a leak guard); an owner/admin can pass allow_public: true to let public apps read it too. Turn sharing on for an app whose data other apps should reuse — e.g. a CRM's contacts list that an invoicing app also needs.

NameTypeReqDescription
allow_publicboolean–Owner/admin only. true lets apps with public routes read this shared data (default false — public apps are blocked).
appstringyes–
sharedbooleanyestrue to share this app's database with the workspace; false to keep it private.
NameTypeReqDescription
allow_publicboolean––
appstring––
sharedboolean––

No examples provided.

set_public_paths ~126

Sets which of an app's paths are reachable WITHOUT login. By default an app is fully private (workspace login required everywhere). Pass the complete desired list of specific paths (e.g. ["/survey"]); each listed path and everything under it becomes public, everything else stays private. An empty list makes the app fully private again. The whole app cannot be made public — root or wildcard paths are rejected.

NameTypeReqDescription
appstringyes–
pathsarrayyesFull list of public paths, each starting with / (e.g. "/survey"). Empty to make fully private.
NameTypeReqDescription
appstring––
publicboolean––
public_pathsarray––

No examples provided.

set_schedules ~135

Sets the app's scheduled tasks. Each is { name, cron, path }: on the cron (standard 5-field, UTC) Croft makes an internal POST to the app's path, and the app does the work (e.g. send a daily email, sync an API). Use this for anything recurring instead of writing your own cron — it survives deploys and reboots and is shown in the panel. Also implement the endpoint (e.g. a POST route at that path). Pass the full desired list; an empty list clears all schedules.

NameTypeReqDescription
appstringyes–
schedulesarrayyes–
NameTypeReqDescription
appstring––
schedulesarray––

No examples provided.

set_secret ~50

Set (or replace) an env secret for an app. Value is stored encrypted and injected at deploy.

NameTypeReqDescription
appstringyes–
keystringyes–
valuestringyes–
NameTypeReqDescription
keystring––
okboolean––

No examples provided.

status ~83

Reports an app's deploy and health status. `live` is true only when the latest deploy has fully succeeded; `deploy_state` gives the current stage (queued, running, succeeded, or failed). Read-only and safe to call repeatedly — each call returns the current stage, so it can be polled to follow a deploy's progress.

NameTypeReqDescription
appstringyes–
NameTypeReqDescription
appstring––
deploy_statestring––
healthstring––
last_deployobject|null––
liveboolean––
public_pathsarray––
releasesinteger––
schedulesarray––
sharedboolean––
urlstring––

No examples provided.

write_files ~72

Writes files into an app's git repo and commits them (as 'Claude via Croft'). files is a list of {path, content}. Committed files are staged in the repo; they are not built or published until the app is deployed.

NameTypeReqDescription
appstringyes–
filesarrayyes–
NameTypeReqDescription
filesarray––
liveboolean––
okboolean––
shastring––

No examples provided.

Common questions

What is the Croft MCP server?

Croft is an MCP server listed in the public MCP registry as net.oncroft/croft. Deploy and host the apps your AI assistant builds, a real server, database, and shareable URL. This page covers its hosted endpoint (https://mcp.oncroft.net).

Is the Croft MCP server safe to use?

Croft scores 39 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 Croft MCP server expose?

Croft exposes 26 tools: get_platform_conventions, list_apps, create_app, get_app, read_file, and 21 more. Their descriptions and schemas cost roughly 1,900 tokens of context every time the server is loaded.

Does the Croft MCP server require authentication?

Yes. Croft 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 Croft MCP server still maintained?

Croft is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.