← Registry

General Tools

elixirconf.com

Provides general-purpose tools through the Model Context Protocol.

1 endpoint2 known toolsFirst detected September 6, 2026Last detected September 6, 2026

ENDPOINT 1

https://async.elixirconf.com/mcp

No auth detected

MCP server metadata

Name
async-elixirconf-public
Version
1.0.0
Capabilities
tools
Server instructions

Public discovery surface for async.elixirconf — the year-round ElixirConf community: the talk archive, conference chat, schedules. These tools carry identity and connection info only. Working with a member's schedule needs their bearer token on this same endpoint — call how_to_connect.

Known tools 2

about_async

What async.

Inferred read-only
how_to_connect

How to connect an agent to a member's account: the authenticated endpoint, token setup, scopes, and the tool list.

Inferred read-only

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.async-elixirconf-public]
url = "https://async.elixirconf.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "async-elixirconf-public": {
      "type": "http",
      "url": "https://async.elixirconf.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: async-elixirconf-public
Remote MCP URL: https://async.elixirconf.com/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": {
    "async-elixirconf-public": {
      "url": "https://async.elixirconf.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "async-elixirconf-public": {
      "type": "http",
      "url": "https://async.elixirconf.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "async-elixirconf-public",
  "transport": "streamable-http",
  "url": "https://async.elixirconf.com/mcp"
}
MCP Inspector

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

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

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