ENDPOINT 1
https://lukefwalton.com/api/archive/mcp
MCP server metadata
- Name
- lukefwalton-archive
- Version
- archive-search/1
Search Luke F. Walton's archive: songs, essays, papers, podcast episodes and their transcripts, pages. The one tool returns ranked hits with provenance, never an answer; you do the reasoning. Read `exposure` on each hit before using it: text is a public passage you may quote with its entity.url; semantic is a released description of a private passage, not a quotation and not the creators' wording; locator is a location only, so do not infer what is there. Cite hits by entity.url. Run several narrow searches (at most 20 hits each) rather than one wide one, and narrow with type, date_from/date_to, creator, and speaker. Nothing is synthesized server-side and query text is not logged by default.
Known tools 1
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.lukefwalton-archive]
url = "https://lukefwalton.com/api/archive/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"lukefwalton-archive": {
"type": "http",
"url": "https://lukefwalton.com/api/archive/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: lukefwalton-archive
Remote MCP URL: https://lukefwalton.com/api/archive/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": {
"lukefwalton-archive": {
"url": "https://lukefwalton.com/api/archive/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"lukefwalton-archive": {
"type": "http",
"url": "https://lukefwalton.com/api/archive/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "lukefwalton-archive",
"transport": "streamable-http",
"url": "https://lukefwalton.com/api/archive/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.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.