Skip to content
External endpointresponds

UseMyContext

The personal context layer for AI: your profile and files, read by any MCP client over OAuth.

Endpoint URL
https://mcp.usemycontext.ai/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:05 AM UTC
Check
MCP initialize · 8s limit
Latency
151 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.usemycontext/usemycontext

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
UseMyContext.ai
Version
0.5.0
Capability keys
tools
Tool names
profile, list_profiles, info, account, list_files, search_files, search, get_file, fetch, ask_docs, query_table, suggest_update, shared_context
Instructions excerpt

UseMyContext.ai serves the connected user's own personal context: a compiled profile, their uploaded files, and contexts other people shared with them. Call `profile` first to ground who the user is. Call `list_profiles` when the user asks what profiles they have: it lists their own profiles (projects) with each one's name, @handle, and privacy status, and marks which one this connection reads by default (metadata only, no file content). Use `list_files` or `search_files` to find a file by name, `get_file` to read one file's full text, `ask_docs` to retrieve cited passages that answer a question from the user's documents, and `query_table` for exact counts, sums, filters, or group-bys over one tabular file. For clients that require the deep-research search/fetch contract, `search` and `fetch` are read-only aliases of `search_files` and `get_file` returning the same data in that shape. Use `shared_context` to list and read contexts shared with the user. When you learn something durable

Reported Aug 17, 2026, 05:05 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 46ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 195ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 396ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 151ms