Skip to content

UseMyContext.ai MCP server

io.github.usemycontext/usemycontextusemycontextstreamable-httpv1.1.0Scanned

Personal context for AI, written by you and never scraped: your profile and files, any MCP client.

13 tools: 3 change things and 10 only read.

Tools: 0 delete, 0 irreversible, 3 write, 10 read.
  • Reads private data · 7
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Sign-in required, OAuth metadata published. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the UseMyContext.ai MCP server can do

The UseMyContext.ai MCP server is published by the GitHub account usemycontext. It has 13 tools. It can create or change data (3 tools: account, query_table and suggest_update), but cannot delete data. 10 tools only read.

7 tools read private data (list_files, search_files, search and 4 more).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint asks for sign-in and publishes OAuth metadata.

Last scanned Nov 6, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

13 tools

Changes things 3Claude Code: ask
  • accountReport the user's current plan and usage: their tier (Free or Premium), how many projects and how much storage they are using against their limits, their subscription status if any…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Report the user's current plan and usage: their tier (Free or Premium), how many projects and how much storage they are using against their limits, their subscription status if any, and where they manage their plan. Use this when the user asks what plan they are on, how much storage or how many projects they have used, or whether they are near a limit. Metadata only - no files, facts, or profile content. This is READ-ONLY: you cannot change the plan or start a purchase; plan and billing changes are done by the user themselves at usemycontext.ai. Read-only; nothing is written, so it is safe to call.

    Annotations the server declares

    • title: Your plan and usage
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • query_tableRun an EXACT, deterministic query over ONE tabular file (a CSV, or the first table of a spreadsheet/PDF/Word document).Reads private data1 finding

    Why it is in this group

    • The name "query_table" says "query": a word for reading.
    • The description's first verb is "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • private-dataThe name "query_table" says "query" and "table": it reads databases.
    • private-dataThe description's first sentence says "file": it reads files.
    • private-dataThe input names a file (input.fileId), and the tool reads: it reads files.

    Findings

    • Warn

      The server marks "query_table" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "query_table" says "query": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Run an EXACT, deterministic query over ONE tabular file (a CSV, or the first table of a spreadsheet/PDF/Word document). Use this instead of ask_docs whenever the question needs COUNTING, SUMMING, AVERAGING, MIN/MAX, FILTERING, or exact row lookups over structured data ('how many rows...', 'total amount by region', 'list orders where status is failed') - semantic search undercounts tables, while this executes over EVERY row and returns exact numbers. Use ask_docs for prose/meaning questions and get_file to read a whole document. The `query` argument is a JSON object: { select?: [column names to return as raw rows], where?: [{col, op, value}, ...] filters combined with AND - ops eq | neq | contains compare text case-insensitively, gt | gte | lt | lte compare numerically (rows whose cell is not a number are skipped and counted in skippedNonNumeric), groupBy?: 'column' gives one result row per distinct value, aggregates?: [{fn, col}] with fn count | sum | avg | min | max ('col' required except for count), limit?: max raw rows (default 50, max 200) }. Column names match the file's header row case-insensitively. Examples: {"where":[{"col":"status","op":"eq","value":"failed"}],"aggregates":[{"fn":"count"}]} counts failed rows; {"groupBy":"region","aggregates":[{"fn":"sum","col":"amount"}]} totals amount per region; {"select":["name","email"],"where":[{"col":"country","op":"eq","value":"FR"}]} returns the matching rows. If you name a column that does not exist, the error lists the file's real columns - retry with one of those. Read-only; nothing is written, so it is safe to call.

    Annotations the server declares

    • title: Query a table exactly
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • suggest_updateSuggest an update to the user's saved context (something you learned about them).No findings

    Why it is in this group

    • The name "suggest_update" says "update": a word for a change.
    Description, as the server wrote it
    Suggest an update to the user's saved context (something you learned about them). It is saved as a PENDING suggestion for the user to review and accept or ignore - it does NOT directly change their profile, and nothing is ever written to their files. When a conversation has surfaced something new and durable about the user and is wrapping up (the user says thanks, goodbye, or that's all, or the task completes), offer to save it here before the context is lost.

    Annotations the server declares

    • title: Suggest a profile update
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
Only reads 10Show 10 read-only tools
  • ask_docsSearch the user's connected documents by MEANING and return the most relevant passages (the actual text), each cited with its source file, for you to read and quote.Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "search": a word for reading.

    What it can reach

    • private-dataThe name "ask_docs" says "doc": it reads documents.
    • private-dataThe description's first sentence says "search" and "document": it reads documents.
    Description, as the server wrote it
    Search the user's connected documents by MEANING and return the most relevant passages (the actual text), each cited with its source file, for you to read and quote. Use this to ANSWER a question from the user's documents - it returns grounded source content, not a file link, not a filename list, and not a pre-written answer (you do the reasoning). Before telling the user you do not know something about them or their work, search here first - the answer is often in their documents. Read-only; nothing is written, so it is safe to call.

    Annotations the server declares

    • title: Ask your documents
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • fetchFetch one document's full extracted text by id (a file id from search / search_files / list_files), in the deep-research result shape.Reads private dataNo findings

    Why it is in this group

    • The name "fetch" says "fetch": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "fetch" and "document": it reads documents.
    Description, as the server wrote it
    Fetch one document's full extracted text by id (a file id from search / search_files / list_files), in the deep-research result shape. ALIAS: this is the SAME read as get_file (same data, same permissions, same audit, same size guard - large files are truncated) - use it when your client requires the id/title/text/url fetch contract (ChatGPT deep research); otherwise prefer get_file, which also serves download links and inline images. Read-only; audited.

    Annotations the server declares

    • title: Fetch a document (deep research)
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_fileGet the full text content of one file by id (large files are truncated; use ask_docs for targeted passages).Reads private dataNo findings

    Why it is in this group

    • The name "get_file" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_file" says "get" and "file": it reads files.
    • private-dataThe description's first sentence says "get" and "file": it reads files.
    • private-dataThe input names a file (input.fileId), and the tool reads: it reads files.
    Description, as the server wrote it
    Get the full text content of one file by id (large files are truncated; use ask_docs for targeted passages). An image returns the picture itself (plus any text read from it at upload); other binary files return a short-lived download link instead. Audited.

    Annotations the server declares

    • title: Open a file
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • infoExplain what UseMyContext is, what this connection can and cannot do, and where the user goes to manage their account.No findings

    Why it is in this group

    • The description's first verb is "explain": a word for reading.
    Description, as the server wrote it
    Explain what UseMyContext is, what this connection can and cannot do, and where the user goes to manage their account. Call this when the user asks what UseMyContext is, what you (the AI) can do with this connection, or where to find pricing, plans, billing, teams, or settings. IMPORTANT: this connection is READ-ONLY - you cannot create/rename/delete a profile, change privacy, manage the plan or billing, set up a team, invite teammates, or connect Google Drive/Notion/kDrive; those are done by the user at usemycontext.ai, so point them to the returned links rather than attempting them or telling them to search. Returns static public information only (no user data). Read-only; nothing is written, so it is safe to call.

    Annotations the server declares

    • title: About UseMyContext
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_filesList the user's files (metadata only: id, name, size, content-type, modified, status).Reads private dataNo findings

    Why it is in this group

    • The name "list_files" says "list": a word for reading.

    What it can reach

    • private-dataThe name "list_files" says "list" and "file": it reads files.
    • private-dataThe description's first sentence says "list" and "file": it reads files.
    Description, as the server wrote it
    List the user's files (metadata only: id, name, size, content-type, modified, status). Each file's status shows its readiness: 'available' means get_file can read it right now, and a just-processed file can take up to about a minute more to become searchable via ask_docs (queueEtaSeconds, when present, estimates the remaining wait). Read-only; nothing is written, so it is safe to call.

    Annotations the server declares

    • title: List your files
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_profilesList the user's own profiles (their projects).No findings

    Why it is in this group

    • The name "list_profiles" says "list": a word for reading.
    Description, as the server wrote it
    List the user's own profiles (their projects). Returns metadata only for each profile: its projectId, its name, its public @handle, its privacy status (private, shared, network, public, or org), and whether it is the one THIS connection reads by default. Use it when the user asks how many profiles they have, what their profiles are called, or which profile you are connected to - and whenever another tool needs a projectId to target a specific profile, because each entry carries its projectId. Do NOT use it to read the user's context, to learn about them, or to set them up with UseMyContext - the profile tool does all three. No file content, no facts, no compiled context. Read-only; nothing is written, so it is safe to call.

    Annotations the server declares

    • title: List your profiles
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • profileReturn the user's compiled personal context - a compact structured summary of who they are, synthesized from their accepted facts.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Return the user's compiled personal context - a compact structured summary of who they are, synthesized from their accepted facts. Call it at the start of any conversation that involves the user personally, to ground who they are. This is ALSO the tool that sets a user up with UseMyContext: call it when they say 'set me up with UseMyContext', 'get me started', 'get to know me', 'onboard me', or otherwise ask you to learn about them. On a brand-new or empty profile the reply carries the setup instructions to follow; on an established one it carries their context. Do not reach for list_profiles for any of that - it only lists each profile's name, @handle, and privacy status. No file content. Read-only; nothing is written, so it is safe to call. Also reports the profile's privacy status (private, shared, network, public, or org) so you can describe it correctly.

    Annotations the server declares

    • title: Your profile
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • search_filesSearch the user's files by filename.Reads private dataNo findings

    Why it is in this group

    • The name "search_files" says "search": a word for reading.

    What it can reach

    • private-dataThe name "search_files" says "search" and "file": it reads files.
    • private-dataThe description's first sentence says "search" and "file": it reads files.
    Description, as the server wrote it
    Search the user's files by filename. Returns matching file metadata (including each file's processing status), ranked by name match. Read-only; nothing is written, so it is safe to call.

    Annotations the server declares

    • title: Search your files
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • shared_contextList and read curated personal context shared with you.No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    List and read curated personal context shared with you. With no arguments, lists who shared what (names + ids only, no content). With a `from` selector (a grantId from that list), returns that person's shared profile text. SAVED BY NAME: if the user has saved a context under a short name, pass `saved` (that exact name) to pull it - the service resolves the name to the real source (a share, a teammate, a @handle, or one of the user's own projects) and re-checks access live every time. If that access is gone (revoked, expired, left the team, or closed), it returns a calm "no longer available" note instead of an error. NETWORK: if you already know a member's project @handle, pass `handle` to pull the context they have opened to the UseMyContext network - their live composite, read-only. Each @handle addresses ONE specific project, so the handle alone identifies what to read. ORGANISATION: if you and another person are members of the same UseMyContext team/organisation on an active team plan, pass `org` (the organisation id) and `member` (that teammate's member id) to read their live composite - their curated context only, never their files or facts. Profiles whose owners set them to public visibility are browsable anonymously at https://usemycontext.ai/directory; for private, shared, network, or team contexts you must already know the saved name / handle / org + member ids. Read-only; nothing is written, so it is safe to call. You only ever see what was shared with you, saved by you, opened to the network, or a teammate's context within your own organisation.

    Annotations the server declares

    • title: Read shared context
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data7
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, OAuth metadata published

Looked at Nov 20, 2026, 19:12 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
401
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
yes
resource_metadata in WWW-Authenticate
https://mcp.usemycontext.ai/.well-known/oauth-protected-resource
RFC 9728 protected resource metadata
https://mcp.usemycontext.ai/.well-known/oauth-protected-resource
Authorization servers
https://mcp.usemycontext.ai
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no

Posture changes

  1. Nov 13, 2026
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://mcp.usemycontext.ai/.well-known/oauth-protected-resource
    • RFC 9728 protected resource metadata: https://mcp.usemycontext.ai/.well-known/oauth-protected-resource/mcp to https://mcp.usemycontext.ai/.well-known/oauth-protected-resource

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "query_table" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "query_table" says "query": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 401; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 3 -> 0 (and 4 more).View diff
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://mcp.usemycontext.ai/.well-known/oauth-protected-resource
    • RFC 9728 protected resource metadata: https://mcp.usemycontext.ai/.well-known/oauth-protected-resource/mcp to https://mcp.usemycontext.ai/.well-known/oauth-protected-resource

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http usemycontext https://mcp.usemycontext.ai/mcp
claude mcp add --transport http usemycontext https://mcp.usemycontext.ai/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__usemycontext__profile",
      "mcp__usemycontext__list_profiles",
      "mcp__usemycontext__info",
      "mcp__usemycontext__list_files",
      "mcp__usemycontext__search_files",
      "mcp__usemycontext__search",
      "mcp__usemycontext__get_file",
      "mcp__usemycontext__fetch",
      "mcp__usemycontext__ask_docs",
      "mcp__usemycontext__shared_context"
    ],
    "ask": [
      "mcp__usemycontext__account",
      "mcp__usemycontext__query_table",
      "mcp__usemycontext__suggest_update"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as usemycontext. Review it before you use it.

Capability tags behind 7 rules
  • mcp__usemycontext__list_files private-data
  • mcp__usemycontext__search_files private-data
  • mcp__usemycontext__search private-data
  • mcp__usemycontext__get_file private-data
  • mcp__usemycontext__fetch private-data
  • mcp__usemycontext__ask_docs private-data
  • mcp__usemycontext__query_table private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.usemycontext/usemycontext/verify?hash=2ec9c27037c8152b97971683f75084fa76a0786c37c481eb423f6654e3d4ccef" | jq -e '.changed == false'

Pinned hash 2ec9c27037c8, from Nov 6, 2026, 15:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.usemycontext/usemycontext/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.usemycontext/usemycontext
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.usemycontext/usemycontext.svg)](https://radar.anlyon.com/servers/io.github.usemycontext/usemycontext)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:51 UTC.

UseMyContext.ai MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the UseMyContext.ai MCP server safe?

No scan can promise that. What its definitions show: 13 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the UseMyContext.ai MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the UseMyContext.ai MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the UseMyContext.ai MCP server have?

13 tools: 3 write, 10 read. account, query_table, suggest_update, profile, list_profiles, info, list_files, search_files and 5 more.

Does the UseMyContext.ai MCP server need sign-in or OAuth?

Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.

Does the UseMyContext.ai MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the UseMyContext.ai MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 6, 2026.