← Registry

Content Tools

hongy.dev

Manages and retrieves published content such as skills and workflows, with persistent memory features.

1 endpoint13 known toolsFirst detected August 19, 2026Last detected August 19, 2026

ENDPOINT 1

https://hongy.dev/api/mcp

No auth detected

MCP server metadata

Name
hongy.dev
Version
0.2.0
Capabilities
tools.listChanged
Server instructions

hongy.dev publishes portable AI coding workflows, skills and agent configuration, and hosts two private stores for the authenticated owner. Content tools (list_content, get_content, search_content) are public. get_content returns documents exactly as authored, so a skill comes back as a valid SKILL.md. Memory Fabric (memory_*) is episodic: what happened, what was decided, what was stated. hongy IQ (iq_*) is semantic: what is now known to be true, addressed by a stable slug and backed by evidence. Search both at the start of a task; write to the one that matches the shape of what you learned. Both require an OAuth session. Scopes are dotted paths rooted at "personal", and reads inherit upward by default. Mint a chat scope at the start of a session — personal.project_<repo>.chat_<date>_<topic> — and pass it on every write, so this conversation is separable later. A bare scope name is read as a project, and omitting it writes at "personal". Forgetting closes a memory rather than erasing it. Superseding an earlier memory keeps it, so the record still says what was believed and when.

Known tools 13

list_content

List published skills, workflows, config files and stack notes on hongy.dev.

Inferred read-only
get_content

Fetch one published document by slug, exactly as authored — frontmatter included, so a skill comes back as a valid SKILL.md ready to write to disk.

Potential side effects
search_content

Full-text search across every published document on hongy.dev.

Inferred read-only
memory_write

Record one durable fact in Memory Fabric so it survives this session: a preference stated, a decision made, a constraint discovered, a correction given, something observed.

Inferred read-only
memory_search

Recall from Memory Fabric.

Inferred read-only
memory_timeline

What happened in a scope, in order.

Inferred read-only
memory_get

Fetch a single memory by id, optionally with the chain it superseded.

Inferred read-only
memory_forget

Stop believing a memory.

Inferred read-only
memory_delete

Deprecated alias for memory_forget.

Inferred read-only
iq_write

Record learned intelligence in hongy IQ: a technique that works, a failure mode and its fix, a benchmarked trade-off, a convention worth keeping.

Potential side effects
iq_search

Search hongy IQ for applicable learned intelligence.

Inferred read-only
iq_get

Fetch a single hongy IQ entry by slug, with its evidence and confidence.

Inferred read-only
iq_delete

Delete a hongy IQ entry by slug.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.hongy-dev]
url = "https://hongy.dev/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "hongy-dev": {
      "type": "http",
      "url": "https://hongy.dev/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: hongy-dev
Remote MCP URL: https://hongy.dev/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "hongy-dev": {
      "url": "https://hongy.dev/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "hongy-dev": {
      "type": "http",
      "url": "https://hongy.dev/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "hongy-dev",
  "transport": "streamable-http",
  "url": "https://hongy.dev/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for hongy.dev was fetched 2026-08-21T13:27:21.949Z.

Trust status Trusted

hongy.dev is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.