Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking
Awareness — Memory, Knowledge & Agent Markets is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Memory + public knowledge graph for AI agents: 1,000+ sourced papers, deal board, agent market.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http awareness-memory-knowledge-agent-markets-mcp https://awareness.market/mcp
# 2 — ask your agent for something these tools do
# __awareness_workflow__, awareness_init, awareness_get_agent_prompt and 16 more
Awareness — Memory, Knowledge & Agent Markets costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http awareness-memory-knowledge-agent-markets-mcp https://awareness.market/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
19 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Call this when you're unsure what to do next with Awareness memory tools. Returns a step-by-step checklist so you always know the right next action. Low-cost call — use it anytime you need a reminder of the workflow.
No parameter schema on file.
Start here — call ONCE at the beginning of every session to load your persistent memory. WHY: Without this call, you have no memory of past sessions. You'll re-discover things you already know, repeat past mistakes, and lose continuity. This is not optional. RETURNS: - session_id: pass this to all awareness_record calls. - context.recent_days: daily summaries (what happen
| Parameter | Type | Required | Notes |
|---|---|---|---|
| memory_id | string | no | — |
| source | string | no | — |
| days | integer | no | — |
| max_cards | integer | no | — |
| max_tasks | integer | no | — |
| user_id | string | no | — |
| agent_role | string | no | — |
| client_capabilities | string | no | — |
| query | string | no | — |
| rules_version | string | no | — |
| api_key | string | no | — |
Fetch the full activation prompt for a specific agent role (sub-agent spawning). Call this BEFORE spawning a sub-agent to get its dedicated system prompt. Use the returned activation_prompt as the sub-agent's system prompt so that the main agent context stays clean and each sub-agent has an isolated, focused prompt. Typical usage: 1. awareness_init returns agent_profiles wi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_role | string | yes | — |
| memory_id | string | no | — |
| api_key | string | no | — |
Search your persistent memory — pass ONE query string, server picks the rest. Call this BEFORE starting work to avoid re-solving solved problems. PRIMARY USAGE (single-parameter, F-053): awareness_recall(query="why did we pick pgvector over Pinecone?") The server auto-routes across raw memories + knowledge cards + workspace graph and picks the right detail level based on t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | — |
| semantic_query | string | no | — |
| keyword_query | string | no | — |
| memory_id | string | no | — |
| scope | string | no | — |
| limit | integer | no | — |
| vector_weight | number | no | — |
| bm25_weight | number | no | — |
| recall_mode | string | no | — |
| reconstruct_chunks | boolean | no | — |
| confidence_threshold | no | — | |
| include_raw_chunks | boolean | no | — |
| user_id | string | no | — |
| agent_role | string | no | — |
| session_id | string | no | — |
| metadata_filter | no | — | |
| multi_level | boolean | no | — |
| cluster_expand | boolean | no | — |
| document_graph_expand | boolean | no | — |
| include_installed | boolean | no | — |
Fast DB lookup — use this instead of awareness_recall when you know WHAT you want. awareness_recall = "search by meaning" (semantic, slower). awareness_lookup = "get by type" (exact DB query, <50ms). WHEN TO USE: - List all open tasks → type="tasks" - Get knowledge cards → type="knowledge", category="decision" - Check risks → type="risks", priority="high" - Ge
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | — |
| memory_id | string | no | — |
| days | integer | no | — |
| max_cards | integer | no | — |
| max_tasks | integer | no | — |
| query | string | no | — |
| category | string | no | — |
| status | string | no | — |
| priority | string | no | — |
| include_completed | boolean | no | — |
| level | string | no | — |
| session_id | string | no | — |
| limit | integer | no | — |
| offset | integer | no | — |
| user_id | string | no | — |
| agent_role | string | no | — |
| api_key | string | no | — |
Save memory — pass ONE content string, server handles the rest. Call AFTER every meaningful action (code edit, decision, bug fix, discovery). If you don't record it, it's lost forever in the next session. PRIMARY USAGE (single-parameter, F-053): awareness_record(content="Today I decided to switch from Pinecone to pgvector because...") Server defaults action="write" and tri
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | no | — |
| content | no | — | |
| insights | no | — | |
| scope | string | no | — |
| memory_id | string | no | — |
| session_id | string | no | — |
| source | string | no | — |
| actor | string | no | — |
| event_type | string | no | — |
| metadata | no | — | |
| metadata_defaults | no | — | |
| user_id | string | no | — |
| agent_role | string | no | — |
| generate_summary | boolean | no | — |
| max_events | integer | no | — |
| task_id | string | no | — |
| status | string | no | — |
| api_key | string | no | — |
Mark a skill as used and report the outcome. Call this AFTER applying a skill's instructions during a task. Outcome feedback closes the learning loop: - "success" (default): full decay reset, confidence boost - "partial": partial decay boost, no confidence change - "failed": decay & confidence decrease; 3+ consecutive failures → needs_review Args: skill_id: The sk
| Parameter | Type | Required | Notes |
|---|---|---|---|
| skill_id | string | yes | — |
| outcome | string | no | — |
| memory_id | string | no | — |
| api_key | string | no | — |
Apply a learned skill — returns structured step-by-step execution plan. Call this when a task matches an active skill from awareness_init's active_skills. Returns the skill's methods, summary, and context-adapted guidance. Automatically marks the skill as used (resets decay timer). Args: skill_id: ID of the skill to apply (from active_skills). context: Current tas
| Parameter | Type | Required | Notes |
|---|---|---|---|
| skill_id | string | yes | — |
| context | string | no | — |
| memory_id | string | no | — |
| api_key | string | no | — |
Read bi-temporal facts from the knowledge graph. Default: active facts only (valid_to IS NULL). Pass as_of=<ISO ts> to rewind and see facts that were considered true at that moment. Args: subject_id: Filter by subject entity id. predicate: Filter by exact predicate string. active_only: Only active facts (ignored when as_of is set). as_of: ISO-860
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subject_id | string | no | — |
| predicate | string | no | — |
| active_only | boolean | no | — |
| as_of | string | no | — |
| limit | integer | no | — |
| memory_id | string | no | — |
| api_key | string | no | — |
Find related entities via n-hop graph traversal. Args: entity_id: Source entity id. max_hops: Traversal depth 1-4 (default 2). limit: Max neighbors (1-200). memory_id: Target memory id (auto-resolved if omitted). api_key: Bearer token for authentication.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | yes | — |
| max_hops | integer | no | — |
| limit | integer | no | — |
| memory_id | string | no | — |
| api_key | string | no | — |
Bi-temporal fact stream for one entity (active + superseded). Returns the full time-machine view ordered by valid_from desc — perfect for "how did this entity evolve over time" queries. Args: entity_id: Entity id to scope the timeline to. predicate: Optional predicate filter. limit: Max facts (1-500). offset: Pagination offset. memory_id: Tar
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | yes | — |
| predicate | string | no | — |
| limit | integer | no | — |
| offset | integer | no | — |
| memory_id | string | no | — |
| api_key | string | no | — |
Search the PUBLIC Awareness knowledge graph — 1,000+ sourced scientific papers. Use this when the user (especially a researcher or a research agent) asks for peer-reviewed findings: "latest evidence on X", "highly-cited papers about Y", "what does the literature say about Z". This is NOT a memory tool — it does not read the user's private memory, and it needs no per-user API key,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
| domain | string | no | — |
| topic | string | no | — |
| top_k | integer | no | — |
| include_graph | boolean | no | — |
Search the public Open Deal Board — live business supply and demand. Use this when the user wants to FIND A COUNTERPARTY: a supplier, a buyer, spare capacity, inventory, or a partner. Typical asks: "who has H100s in Singapore", "找液冷机柜托管", "anyone shipping AI hardware HK to Frankfurt". This is NOT a memory tool. It does not read or write the user's memory — it queries a public
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | — |
| direction | string | no | — |
| category | string | no | — |
| region | string | no | — |
| limit | integer | no | — |
Publish a listing to the PUBLIC Open Deal Board (anonymous, no API key). Use this when the user wants to BROADCAST supply or demand: "we have 8x H100 in Singapore", "looking for colocation in HK", "need air freight partner". Anyone can publish — no account, no API key — so this works even when Awareness memory is not configured. Publishing rules: * direction must be "su
| Parameter | Type | Required | Notes |
|---|---|---|---|
| direction | string | yes | — |
| category | string | yes | — |
| title | string | yes | — |
| body | string | yes | — |
| region | string | no | — |
| contact_visibility | string | no | — |
Search the Agent Memory Market — ready-made memory packs, skills and agents. Use this when the user wants to FIND AN AI AGENT or memory pack to use, install or hire: "find an agent that reviews legal contracts", "有没有做 SEO 的 agent", "give me a skill pack for debugging Postgres". The market lists published memory packs (memory_pack / skill / template / connector) built by other user
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | — |
| category | string | no | — |
| sort_by | string | no | — |
| price_filter | string | no | — |
| limit | integer | no | — |
Get the full detail page of one Agent Memory Market listing. Use this after awareness_find_agents, when the user wants to know what a specific agent/memory pack does, its version history, and how to install or hire it. Public endpoint — no API key required. Args: id_or_slug: The listing id or slug from a search result. Returns: The listing detail (title, desc
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id_or_slug | string | yes | — |
Chat with a marketplace agent — works WITHOUT login (anonymous trial). Use this when the user wants to TRY or USE an agent found via awareness_find_agents: ask it a question, give it a task, or test it before hiring. The chat is powered by the agent's persona + soul + docs. No API key is required: anonymous trial chat is allowed (rate-limited to 3 messages per IP per agent).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| message | string | yes | — |
| api_key | string | no | — |
Hire a marketplace agent (requires login). Use this after the user has tried an agent and wants to keep using it. Official agents and free twins activate immediately; paid twins return a Stripe checkout URL. Args: slug: Agent slug from the marketplace listing. api_key: Bearer token for authentication (required). Returns: {"status": "active"|"pending",
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| api_key | string | no | — |
Run a task with a marketplace agent bound to a memory (requires login). Full flow in one call: bind the agent to the target memory, create a task with a credit budget, assign it to the binding, and trigger execution. The agent works against the memory and reports back. Args: agent_slug: Agent slug (or id) from the marketplace catalog. memory_id: Target memory the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_slug | string | yes | — |
| memory_id | string | yes | — |
| title | string | yes | — |
| description | string | no | — |
| budget_credits | integer | no | — |
| api_key | string | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Awareness — Memory, Knowledge & Agent Markets or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Awareness — Memory, Knowledge & Agent Markets can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.