MCP server · registry snapshot 2026-11-03 · last checked 2026-11-03

com.elfhosted/my-stack

ElfHosted: my stack — the publisher's title

by elfhosted.com · domain (the registry's namespace rule)Website ↗

Your own ElfHosted apps: health, libraries, settings, and changes you approve. Needs an account. — the publisher's description

1 of 2 record checks metversion 1.0.1streamable HTTP

Summary

com.elfhosted/my-stack is a remote MCP server listed in the official MCP registry at version 1.0.1, under the namespace of the domain elfhosted.com.

Record checks

1 of 2 record checks met · 7 do not apply

met: Registry entry is active and says how to run it
not met: Source repository link opens
not applicable: Repository is not archived
not applicable: Code pushed to the repository in the 90 days before our check
not applicable: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Your own values: none declared (not a guarantee)
Last tested: not tested

Tool list

Not read: It requires a setting the publisher marks as required (for example a URL part or a configuration value) that has no default, so we did not start it. So there is no tool-list size and no result from the three APIs.

Add to your client

How fresh this is

Live-tested

Last tested

not tested

Latest version

1.0.1, published 2026-11-03 (registry, as of the 2026-11-03 snapshot)

First listed version

2026-11-03 (earliest version still in the registry; older removed versions would be earlier)

Version history

2 versions listed, all on 2026-11-03; 2 in the 90 days before the 2026-11-03 snapshot.

Most recent 2 versions

1.0.1 · 2026-11-03
1.0.0 · 2026-11-03

(versions still listed in the registry only)

Registry data

snapshot 2026-11-03

Package and repository

checked 2026-11-03

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-02, listed on 2026-11-03 with version 1.0.1 (published 2026-11-03).

Source: the official MCP Registry list on 2026-11-02 and on 2026-11-03.

What it is

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

This entry needs values of your own (marked < > or { } in the config below), so there is no one-click link: paste the config and fill them in.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://{username}-elfbot.{domain}/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "my-stack": {
      "url": "https://{username}-elfbot.{domain}/mcp"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "my-stack": {
      "type": "http",
      "url": "https://{username}-elfbot.{domain}/mcp"
    }
  }
}

Claude Code

claude mcp add --transport http my-stack "https://{username}-elfbot.{domain}/mcp"

Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)

{
  "mcpServers": {
    "my-stack": {
      "type": "streamableHttp",
      "url": "https://{username}-elfbot.{domain}/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}

Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project

{
  "mcpServers": {
    "my-stack": {
      "httpUrl": "https://{username}-elfbot.{domain}/mcp"
    }
  }
}

OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project

[mcp_servers.my-stack]
url = "https://{username}-elfbot.{domain}/mcp"

Zed · Zed settings file (command: zed: open settings file)

{
  "context_servers": {
    "my-stack": {
      "url": "https://{username}-elfbot.{domain}/mcp"
    }
  }
}

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url "https://{username}-elfbot.{domain}/mcp" --transport http

The URL contains parts in { } that the entry marks as variables; replace them with your own values.
The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
Does not applyRepository is not archivedNo public GitHub repository to read.
Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-03. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about com.elfhosted/my-stack

Answered from the data above

Who publishes com.elfhosted/my-stack?

The registry ties the namespace com.elfhosted to the domain elfhosted.com; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Has com.elfhosted/my-stack been security tested?

No. It requires a setting the publisher marks as required (for example a URL part or a configuration value) that has no default, so we did not start it.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

Has it been tested?

Feature #1

It requires a setting the publisher marks as required (for example a URL part or a configuration value) that has no default, so we did not start it. — the server's own choice

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

pending: added in the weekly update

listed 2026-11-03; not classified yet

Pricing modelAI-classified

pending: added in the weekly update

the website is not read yet

Programming language

does not apply

no existing GitHub repository (server declares no repository link, so there is nothing to fetch)

Hosting type

remote (hosted by the publisher)

registry · 2026-11-03

MCP capability

not checked

not read (no session)

Transport

streamable HTTP

registry · 2026-11-03

Required credentials

none declared

registry · 2026-11-03 · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-11-03

Lifecycle status

active

registry · 2026-11-03

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

not stated

no readable GitHub owner to describe

Maintenance

does not apply

server declares no repository link, so there is nothing to fetch

Environment

the publisher's infrastructure

where it runs, from the hosting type · 2026-11-03

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “com.elfhosted/my-stack: MCP server record.” Data checked 2026-11-03. https://protocolprobe.com/mcp/servers/com.elfhosted/my-stack

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/com.elfhosted/my-stack)](https://protocolprobe.com/mcp/servers/com.elfhosted/my-stack)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology