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.

Causara Economic Control

REMOTE · CAUSARA.FLOOT.APP

Economic exposure and control decisions for autonomous AI actions in Shadow Mode.

+2 this week 83 Trust /100

Last scanned (45 minutes ago)

Scores higher than 87% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Finance and Payments

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 Security74
Transport & Reachability100
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 286 tokens (~95/item across 3 items; 3 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 Coverage73
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 20% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

  • 3 Nov 26 0
    • Stability: 0.97 → pass security
  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 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.

  • 21 Oct 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.

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 5 Nov 2026 · Probed https://causara.floot.app/_api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=floot.app CN=Amazon RSA 2048 M01,O=Amazon,C=US 16 Jun 2026 30 Dec 2026 RSA 2048 SHA256-RSA 35a2e10e5621c2d1eb0ba80daffc49d
SANs: floot.app, combini.app, *.combini.app, *.floot.app
CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 77312380b9d6688a33b1ed9bf9ccda68e0e0f
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of causara.floot.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
floot.app. absent 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://causara.floot.app/_api/mcp Verified 200
http (plaintext) http://causara.floot.app/_api/mcp HTTPS enforced 301 https://causara.floot.app/_api/mcp
MCP tools · 3 exposed · ~224 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
evaluate_agent_action ~104

Run a proposed autonomous AI action through Causara's frozen Shadow Mode economic-control engine. Returns downstream dependency path, economic exposure, potential loss, confidence, and an ALLOW/REVIEW/ESCALATE/BLOCK recommendation. Causara does not execute or block the proposed business action. The evaluation is recorded in Causara's Shadow risk ledger.

NameTypeReqDescription
business_contextobjectyes–
data_sourceobject––
eventobjectyes–

No output schema declared.

No examples provided.

get_control_model ~49

Return the live Causara V2.0 Shadow Mode model metadata, including supported action routes and frozen validation status. Use this before evaluation when you need to check whether an action type is supported.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

normalize_business_context ~71

Validate and normalize a structured business-context CSV into Causara's canonical economic context. This does not evaluate or execute an AI action. Use it when source data is available as a field/value or single-row CSV export.

NameTypeReqDescription
csvstringyesBusiness context CSV text.
filenamestring––

No output schema declared.

No examples provided.

Install

How do I install the Causara Economic Control MCP server?

Causara Economic Control is a hosted endpoint at https://causara.floot.app/_api/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 · causara.floot.app

# add to Claude Code
claude mcp add --transport http mahadrehman239-del-causara-economic-control 'https://causara.floot.app/_api/mcp'
Common questions

What is the Causara Economic Control MCP server?

Causara Economic Control is an MCP server listed in the public MCP registry as io.github.mahadrehman239-del/causara-economic-control. Economic exposure and control decisions for autonomous AI actions in Shadow Mode. This page covers its hosted endpoint (https://causara.floot.app/_api/mcp).

Is the Causara Economic Control MCP server safe to use?

Causara Economic Control scores 83 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 Causara Economic Control MCP server expose?

Causara Economic Control exposes 3 tools: get_control_model, normalize_business_context, evaluate_agent_action. Their descriptions and schemas cost roughly 224 tokens of context every time the server is loaded.

Does the Causara Economic Control MCP server require authentication?

No. We connected to Causara Economic Control without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Causara Economic Control MCP server still maintained?

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