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.

SOKI (想起) — Personal Memory

REMOTE · MCP.KITEMIR.JP · SCANNED SEP 20

Personal memory outside the AI. Due dates, loose ends and old notes come back on their own.

Available components

remote · mcp.kitemir.jp 37
37 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 Security92
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 SOKI (想起) — Personal Memory MCP server?

SOKI (想起) — Personal Memory is a hosted endpoint at https://mcp.kitemir.jp/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.kitemir.jp

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

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.

  • 16 Sept 26 37

    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 20 Sept 2026 · Probed https://mcp.kitemir.jp/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.mcp.kitemir.jp CN=GlobalSign Atlas R46 AlphaSSL CA 2026 Q3,O=GlobalSign nv-sa,C=BE 2 Aug 2026 17 Feb 2027 RSA 2048 SHA256-RSA 137308bb09339223c3f2682b1a0c6ef
SANs: www.mcp.kitemir.jp, mcp.kitemir.jp
CN=GlobalSign Atlas R46 AlphaSSL CA 2026 Q3,O=GlobalSign nv-sa,C=BE (CA) CN=GlobalSign Root R46,O=GlobalSign nv-sa,C=BE 22 Apr 2026 22 Apr 2028 RSA 4096 SHA384-RSA 85ac70570ac1afa28f512ebe1d75b021

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.kitemir.jp. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
jp. present 33631 8 Verified
kitemir.jp. 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 error="invalid_token", error_description="missing bearer token", resource_metadata="https://mcp.kitemir.jp/.well-known/oauth-protected-resource/mcp", scope="memory:read memory:write" 

Bearer error="invalid_token", error_description="missing bearer token", resource_metadata="https://mcp.kitemir.jp/.well-known/oauth-protected-resource/mcp", scope="memory:read memory:write"
Header Value
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy no-referrer
www-authenticate Bearer error="invalid_token", error_description="missing bearer token", resource_metadata="https://mcp.kitemir.jp/.well-known/oauth-protected-resource/mcp", scope="memory:read memory:write"

Protected resource metadata

Document https://mcp.kitemir.jp/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://mcp.kitemir.jp/mcp
Authorisation server https://mcp.kitemir.jp

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.kitemir.jp/mcp Auth required 401
http (plaintext) http://mcp.kitemir.jp/mcp HTTPS enforced 301 https://mcp.kitemir.jp/mcp
MCP tools

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 →

No tool schema has been captured from this endpoint yet.

Common questions

What is the SOKI (想起) — Personal Memory MCP server?

SOKI (想起) — Personal Memory is an MCP server listed in the public MCP registry as jp.kitemir/soki. Personal memory outside the AI. Due dates, loose ends and old notes come back on their own. This page covers its hosted endpoint (https://mcp.kitemir.jp/mcp).

Is the SOKI (想起) — Personal Memory MCP server safe to use?

SOKI (想起) — Personal Memory scores 37 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.

Does the SOKI (想起) — Personal Memory MCP server require authentication?

Yes. SOKI (想起) — Personal Memory 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 SOKI (想起) — Personal Memory MCP server still maintained?

SOKI (想起) — Personal Memory is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.