_ registry / mcp http-sse · checked 1h ago

DejaView

https://api.dejaview.io

Registry code: 631fe80f0feae468

api record

You have a persistent knowledge graph via DejaView. Call agent_context() at session start to load your memory. Use remember() whenever you learn something worth keeping. Use recall() for full details on any entity.

endpoint
https://api.dejaview.io/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is DejaView live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is DejaView free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does DejaView have?
11 tools: ask, search, recall, agent_context, forget, remember, remember_many, share, ….
Is DejaView safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.7%

90 days 98.8%· all time 98.8%

latency
490ms

last good check

priced tools
0

of 11 tools

_ answered our checks, 90 days 405 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
ai & agents memory & context
used for
  • store facts in a knowledge graph
  • recall everything about an entity
  • ask questions over stored memory
  • share a subgraph by link
takes → gives
text → data, text
tools
6 reads5 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 11 tools
8 auth-required 3 never probed 8 of 11 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • agent_context reads auth-required 15h ago

    Get a full context summary of your knowledge graph. Returns entity counts, most-connected entities, and recent activity. Call this at the start of every conversation to bootstrap your memory.

    mcp-tool

    {
  "type": "object",
  "title": "agent_contextArguments",
  "properties": {}
}
    arguments 5 lines
  • forget changes data auth-required never probed

    Remove a specific fact from the knowledge graph. Deletes the relationship between subject and object but leaves both entities intact. Use to correct wrong or outdated facts.

    mcp-tool

    {
  "type": "object",
  "title": "forgetArguments",
  "required": [
    "subject",
    "predicate",
    "object"
  ],
  "properties": {
    "object": {
      "type": "string",
      "title": "Object",
      "description": "The object entity of the fact to remove."
    },
    "subject": {
      "type": "string",
      "title": "Subject",
      "description": "The subject entity of the fact to remove."
    },
    "predicate": {
      "type": "string",
      "title": "Predicate",
      "description": "The relationship type to remove."
    }
  }
}
    arguments 26 lines
  • remember changes data auth-required never probed

    Store a fact as subject -> predicate -> object in the knowledge graph. Use for any relationship, preference, decision, or event worth keeping across sessions. Examples: remember("Alice", "works_at", "Orbit Labs") remember("Project Atlas", "has_status", "in progress", "As of Q1 2026")

    mcp-tool

    {
  "type": "object",
  "title": "rememberArguments",
  "required": [
    "subject",
    "predicate",
    "object"
  ],
  "properties": {
    "object": {
      "type": "string",
      "title": "Object",
      "description": "The target entity or value. E.g. 'Orbit Labs', 'in progress'"
    },
    "context": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Context",
      "default": null,
      "description": "Optional extra context or timestamp. E.g. 'As of Q1 2026'"
    },
    "subject": {
      "type": "string",
      "title": "Subject",
      "description": "The entity the fact is about. E.g. 'Alice', 'Project Atlas'"
    },
    "predicate": {
      "type": "string",
      "title": "Predicate",
      "description": "The relationship type. E.g. 'works_at', 'founded', 'prefers', 'has_status', 'decided'"
    }
  }
}
    arguments 39 lines
  • remember_many changes data auth-required never probed

    Store multiple facts at once. More efficient than looping remember(). Each fact needs: subject, predicate, object. Optional: context.

    mcp-tool

    {
  "type": "object",
  "title": "remember_manyArguments",
  "required": [
    "facts"
  ],
  "properties": {
    "facts": {
      "type": "array",
      "items": {},
      "title": "Facts",
      "description": "List of facts to store. Each item needs: subject, predicate, object (all strings). Optional: context (str). Max 100 per call."
    }
  }
}
    arguments 15 lines
  • share changes data auth-required never probed

    Create a public shareable link for any entity's subgraph. Returns a URL anyone can open — no account needed. Shows an interactive visual graph of the entity and its connections.

    mcp-tool

    {
  "type": "object",
  "title": "shareArguments",
  "required": [
    "entity"
  ],
  "properties": {
    "depth": {
      "type": "integer",
      "title": "Depth",
      "default": 2,
      "maximum": 4,
      "minimum": 1,
      "description": "How many relationship hops to include. Default 2, higher = larger graph."
    },
    "title": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Title",
      "default": null,
      "description": "Optional custom title for the shared graph page."
    },
    "entity": {
      "type": "string",
      "title": "Entity",
      "description": "The exact name of the entity to share."
    }
  }
}
    arguments 35 lines
  • forget_entity changes data auth-required never probed

    Remove an entity AND all its relationships from the knowledge graph. Use with care — this permanently wipes the node and every edge connected to it. Good for removing entirely wrong or duplicate entities.

    mcp-tool

    {
  "type": "object",
  "title": "forget_entityArguments",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "title": "Name",
      "description": "The exact name of the entity to permanently delete, along with all its relationships."
    }
  }
}
    arguments 14 lines
  • graph_stats reads auth-required 15h ago

    Get a high-level summary of the knowledge graph. Returns entity count, entity types, relationship count, and relationship types.

    mcp-tool

    {
  "type": "object",
  "title": "graph_statsArguments",
  "properties": {}
}
    arguments 5 lines
  • timeline reads auth-required 15h ago

    Get recent facts in reverse chronological order. Use at session start alongside agent_context() to see what was recently remembered.

    mcp-tool

    {
  "type": "object",
  "title": "timelineArguments",
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 20,
      "maximum": 100,
      "minimum": 1,
      "description": "Number of facts to return. Default 20, max 100."
    }
  }
}
    arguments 14 lines
  • ask reads unknown 12h ago

    Ask a natural language question about your knowledge graph. Returns a synthesized answer backed by cited graph facts — no hallucination. Every claim traces to a real stored fact with a timestamp.

    mcp-tool

    {
  "type": "object",
  "title": "askArguments",
  "required": [
    "question"
  ],
  "properties": {
    "question": {
      "type": "string",
      "title": "Question",
      "description": "A natural language question about entities or relationships in your graph. E.g. 'What do I know about Alice?' or 'What projects is Alice working on?'"
    }
  }
}
    arguments 14 lines
  • search reads unknown 12h ago

    Search for entities in the graph by name (partial match). Use this to discover what's in the graph before calling recall(). Returns names, types, and connection counts.

    mcp-tool

    {
  "type": "object",
  "title": "searchArguments",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "title": "Query",
      "description": "Search term for entity names. Supports partial matching. E.g. 'Ali' will match 'Alice'."
    }
  }
}
    arguments 14 lines
  • recall reads unknown 12h ago

    Get everything known about an entity — all relationships in and out. Use for full context on a person, project, org, concept, or any entity.

    mcp-tool

    {
  "type": "object",
  "title": "recallArguments",
  "required": [
    "entity"
  ],
  "properties": {
    "entity": {
      "type": "string",
      "title": "Entity",
      "description": "The exact name of the entity to look up. Use search() first if unsure of the exact name."
    }
  }
}
    arguments 14 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 631fe80f0feae468.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/631fe80f0feae468/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/631fe80f0feae468/badge.svg)](https://brick.blue/agent/631fe80f0feae468?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.