Secureframe MCP server

What the model can do

Secureframe compliance automation: tests that pass, fail or are at risk, controls and their health, frameworks with test counts, policies and how many people have accepted them, risks, vendors by risk level, and compliance tasks with due dates. Can comment on tests, controls, risks, policies and other records, create or change tests, open and update POA&M items, archive a vendor and add knowledge base questions.

Reads

• secureframe_list_testsSecureframe tests (automated and upload checks): title, key, health (pass, at_risk, fail, disabled), type, owner, controls and frameworks it covers…
• secureframe_list_controlsSecureframe controls: key, name, health (healthy, unhealthy, at_risk, not_tested…), implementation status, owner, frameworks, and passing, failing…
• secureframe_list_frameworksCompliance frameworks in Secureframe (SOC 2, ISO 27001, HIPAA…): title, key, applicable controls and requirements, and passing, failing…
• secureframe_list_policiesSecureframe policies: name, status (published, draft, archived…), when published, frameworks…
• secureframe_list_risksRisks in the Secureframe risk register: identifier, description, status, treatment, categories, departments, responsible team and when updated.
• secureframe_list_vendorsVendors in Secureframe's third-party risk register: name, risk level, status (accepted, pending, rejected), website, services provided…
• secureframe_list_tasksCompliance tasks in Secureframe: title, category, type, what it is about (a test, risk, vendor or access review), due date, whether overdue…
• secureframe_list_usersFind a Secureframe user's id to use as an owner (of a test, POA&M item or knowledge base question): id and name only, active users by default.

Acts, when you ask

These change something in Secureframe. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• secureframe_create_commentAdds a comment to one Secureframe record (a test, control, risk, policy, POA&M item, evidence, framework requirement, audit…
• secureframe_update_commentReplaces the text of one Secureframe comment, for everyone who can see it.
• secureframe_delete_commentPermanently deletes one Secureframe comment, for everyone.
• secureframe_create_testCreates a custom upload test in Secureframe: a test that passes while current evidence is attached to it, and counts towards the compliance score.
• secureframe_update_testChanges one Secureframe test: enable or disable it (disabling needs a justification…
• secureframe_create_poam_itemOpens a POA&M (plan of action and milestones) item in Secureframe with the given owner.
• secureframe_update_poam_itemChanges one Secureframe POA&M item: its status (draft, in_progress, closed), owner, risk level, issue, remediation plan, identifier or dates.
• secureframe_discard_poam_itemDiscards one Secureframe POA&M item, taking it out of the plan.
• secureframe_archive_vendorArchives one vendor in Secureframe's third-party risk register: it leaves the active vendor list and its reviews stop.
• secureframe_create_knowledge_base_questionAdds a question to the Secureframe knowledge base that answers security questionnaires, with an optional owner and review frequency.

Connect it

First connect Secureframe on Dashboard → Connections, then add Memtro to your client once. The Secureframe tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Secureframe connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which tests are failing?
• › Has everyone accepted the security policy?
• › How ready are we for SOC 2?
• › Which high-risk vendors have two-factor off?
• › Open a POA&M item for the failing backup test, owned by Maya Okafor

Questions

Is this an official Secureframe MCP server?

No. It is Memtro's MCP server with Memtro's Secureframe connector behind it: the connector reads Secureframe through its API with the credentials you connect on Dashboard → Connections, and Secureframe publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Secureframe?

Only when you ask, and only what it has been granted: comment on a test, control, risk, policy, POA&M item, evidence or vendor review in Secureframe; edit a Secureframe comment; delete a Secureframe comment; create a custom upload test in Secureframe; enable or disable a Secureframe test, or change its owner, due date or interval; open a POA&M item in Secureframe; update a Secureframe POA&M item; discard a Secureframe POA&M item; archive a vendor in Secureframe; add a question to the Secureframe knowledge base. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server