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.

ca.arrowmem/arrowmem-mcp

REMOTE · MCP.ARROWMEM.CA

Free Ollama hardening checker, plus tools for privacy architecture and the Data Dignity Standard.

Available components

+4 this week 63 Trust /100

Last scanned (17 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Security

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 Security60
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1922 tokens (~137/item across 14 items; 14 tools + 0 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 Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 18 Oct 26 +1

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

  • 16 Oct 26 +1

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

  • 13 Oct 26 +1

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

  • 12 Oct 26 +1
    • Stability: unverified → 0.07 ▲ functional
  • 10 Oct 26 59

    First indexed and scored.

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 18 Oct 2026 · Probed https://mcp.arrowmem.ca/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.arrowmem.ca CN=Amazon RSA 2048 M01,O=Amazon,C=US 31 Aug 2026 16 Mar 2027 RSA 2048 SHA256-RSA 60c009dd9896cb4795d2f78d31fc157
SANs: mcp.arrowmem.ca
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 secure

Validation of mcp.arrowmem.ca. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ca. present 26384 13 Verified
arrowmem.ca. present 2371 13 Verified
mcp.arrowmem.ca. Verified address RRset verified with the apex keys
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.arrowmem.ca/mcp Verified 200
http (plaintext) http://mcp.arrowmem.ca/mcp HTTPS enforced
MCP tools · 14 exposed · ~1,922 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
check_exposed_services ~321

ArrowMem Guard's machine security sweep, given diagnostic output your own machine (or AI tool) already produced locally - this tool never reaches your machine or network, it only reasons over what you send it. Checks whether a model server and common database, search and notebook services are reachable beyond loopback, plus firewall state, disk encryption, screen lock, and pending OS updates - each resolves to PASS, FAIL, or UNVERIFIABLE (never guessed on missing data). The report leads with the highest-severity unresolved finding and names one first action, then lists every result in full with a complete per-OS fix and verify step. States plainly that a service bound wide is not the same claim as internet-reachable (this tool can see local configuration, not your network path). Limits: no signature or malware detection, no behavioural analysis, no filesystem or traffic monitoring. Nothing you submit is stored, logged, or retained; each call is evaluated in isolation. Paid tool - requires a valid API key.

NameTypeReqDescription
disk_encryption_status_textstring––
elasticsearch_listen_addressesarray––
firewall_status_textstring––
jupyter_listen_addressesarray––
mongodb_listen_addressesarray––
ollama_listen_addressesarray––
pending_os_updates_countinteger––
platformstring––
postgres_listen_addressesarray––
redis_listen_addressesarray––
screen_lock_status_textstring––

No output schema declared.

No examples provided.

check_ollama_hardening ~305

Checks whether a self-hosted model server install still matches the hardening guide's defaults, given the diagnostic output your own machine (or AI tool) already produced locally - this tool never reaches your machine or network, it only reasons over what you send it. Checks: host environment variable safety, loopback-only reachability on the model server and reverse proxy ports, the reverse proxy configuration's bind directive and credential enforcement, a unique (non-shared) credential, and disk encryption - each check resolves to PASS, FAIL, or UNVERIFIABLE (never guessed), the same three per-check states the doctor script uses. The OVERALL verdict differs from the script's own stricter rule, which collapses any UNVERIFIABLE into a failed run: this tool reports an UNVERIFIABLE-only result as UNVERIFIABLE, not an asserted failure it never measured. Nothing you submit is stored, logged, or retained; each call is evaluated in isolation and returns a per-check verdict. Cannot verify mesh-only reachability (no live network probe) and cannot detect drift after the moment you ran the diagnostics. Free tool, no API key required.

NameTypeReqDescription
caddy_listen_addressesarray––
caddyfile_textstring––
disk_encryption_status_textstring––
ollama_host_envstring––
ollama_listen_addressesarray––
platformstring––

No output schema declared.

No examples provided.

check_ollama_loopback ~120

Checks one thing: whether your self-hosted model server is reachable from outside the machine. Given the diagnostic output your own machine (or AI tool) already produced locally - this tool never reaches your machine or network, it only reasons over what you send it. Resolves to PASS, FAIL, or UNVERIFIABLE (never guessed). On FAIL, returns the complete fix. Nothing you submit is stored, logged, or retained.

NameTypeReqDescription
ollama_host_envstring––
ollama_listen_addressesarray––

No output schema declared.

No examples provided.

disable_alert_relay ~105

Ends this API key's ArrowMem Guard alert relay enrolment. No arguments. Your family link stops resolving, your old topic gets one fixed notice that the relay ended, and every relay attribute is removed from your key's row; it mints nothing, and calling it again is a no-op. Your key, usage, cap and subscription are untouched; call enrol_alert_relay afterward to enrol again. Paid tool - requires a valid API key. Spends one call.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

enrol_alert_relay ~277

Enrols this API key in the ArrowMem Guard alert relay (the watchdog page and the family 'Is It Really Me' check). Mints a relay token stored beside your key and returns an alert topic derived from it (subscribe to it once, in a push notification app, on your own phone), plus a one-time family link you share with the one person you want able to check on you if a call sounds like you and asks for money. No arguments. On an already-enrolled key it returns the SAME topic and no new family link (never re-shown once given). To replace the topic or the link use rotate_alert_relay; to end the enrolment use disable_alert_relay. Honest limit: ArrowMem can derive this topic from what it stores, so a topic is public-by-name the moment it exists - every page sent over it is a fixed, contentless sentence, never your real findings or any personal detail. The family check cannot be faked the same way; an answer comes back through the server, bound to a one-time token, and only proves someone holding the phone tapped Yes or No. Paid tool - requires a valid API key. Spends one call. A family member's own ask also spends one call from your plan, so you can see a leaked link being used.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_arrowbridge_info ~41

ArrowBridge, the local-first / own-hardware half of ArrowMem's privacy design - what it does today and what is still planned, not live.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_data_dignity_standard ~66

The Data Dignity Standard (v0.5, draft for public comment): a free, open, testable standard for what happens to a person's data when an AI agent interacts with a site on their behalf, and how sites and agents are graded against it.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_hardening_guide ~58

The full, live-tested procedure for hardening a self-hosted model server (mesh-only reachability, loopback-only bind, unique per-install credentials, disk encryption, a doctor script). Free tool, no API key required.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_org_info ~50

ArrowMem Inc. is a Canadian company that makes ArrowMem, a personal AI assistant. This tool returns the company's own published overview: what ArrowMem is, who operates it, and its official site.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_privacy_model ~40

ArrowMem's privacy and security architecture: zero retention, client-side encryption, processing-location disclosure, and how the business is funded without reading user content.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_verified_business_facts ~122

Looks up hand-verified facts about a local business by name and city: legal name, locations, published prices (each with its source URL and the date it was verified), hours, an ownership statement, the audit date, and what is not yet verified. Every record was entered by hand from the business's own published sources, with the business's written consent to be published here. A business not found returns a plain NOT_FOUND result. Free tool, no API key required.

NameTypeReqDescription
business_namestringyes–
citystringyes–

No output schema declared.

No examples provided.

inventory_ai_agents ~231

Lists every AI tool configuration on this machine and every tool each one exposes at the config level, plus which agent hosts could not be checked and why. AI tools whose connectors live in your provider account, not a local file, so they are always reported UNVERIFIABLE by design with where to check instead - never silently omitted. Free and stateless: this call has no memory of a prior one, so it lists what is configured, it does not detect what changed since you last looked. Nothing you submit is stored, logged, or retained.

NameTypeReqDescription
claude_code_project_config_textstring––
claude_code_project_tools_textstring––
claude_code_user_config_textstring––
claude_code_user_tools_textstring––
claude_desktop_config_textstring––
claude_desktop_tools_textstring––
cursor_global_config_textstring––
cursor_global_tools_textstring––
cursor_project_config_textstring––
cursor_project_tools_textstring––

No output schema declared.

No examples provided.

list_packs ~32

The specific government disability-claim packs that run inside ArrowMem, and how the optional cross-device sync tier works.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

rotate_alert_relay ~154

Replaces part of this API key's ArrowMem Guard alert relay enrolment. Argument: {"scope": "topic"|"family"|"both"} (required). scope="topic" replaces the relay token only (the old topic gets one notice that it is changing, then stops being used) - your family link keeps working. scope="family" replaces the family link only (the old one stops working) and returns the new link - your topic is unchanged. scope="both" does both. Your key, usage, cap and subscription are untouched. Requires an existing enrolment (enrol_alert_relay). Paid tool - requires a valid API key. Spends one call.

NameTypeReqDescription
scopestringyes–

No output schema declared.

No examples provided.

Install

How do I install the ca.arrowmem/arrowmem-mcp server?

ca.arrowmem/arrowmem-mcp is a hosted endpoint at https://mcp.arrowmem.ca/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.arrowmem.ca

# add to Claude Code
claude mcp add --transport http ca-arrowmem-arrowmem-mcp 'https://mcp.arrowmem.ca/mcp'
Common questions

What is the ca.arrowmem/arrowmem-mcp server?

ca.arrowmem/arrowmem-mcp is listed in the public MCP registry as ca.arrowmem/arrowmem-mcp. Free Ollama hardening checker, plus tools for privacy architecture and the Data Dignity Standard. This page covers its hosted endpoint (https://mcp.arrowmem.ca/mcp).

Is the ca.arrowmem/arrowmem-mcp server safe to use?

ca.arrowmem/arrowmem-mcp scores 63 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 ca.arrowmem/arrowmem-mcp server expose?

ca.arrowmem/arrowmem-mcp exposes 14 tools: check_exposed_services, check_ollama_hardening, check_ollama_loopback, disable_alert_relay, enrol_alert_relay, and 9 more. Their descriptions and schemas cost roughly 1,922 tokens of context every time the server is loaded.

Does the ca.arrowmem/arrowmem-mcp server require authentication?

No. We connected to ca.arrowmem/arrowmem-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ca.arrowmem/arrowmem-mcp server still maintained?

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