General Tools
techunit.io
Manages TechUnit business inquiries, newsletter subscriptions, and resource discovery.
ENDPOINT 1
https://techunit.io/mcp
MCP server metadata
- Name
- techunit-mcp
- Version
- 1.0.0
TechUnit MCP server. Use discover-techunit-resources for first-party data; contact/newsletter tools return prefilled URLs for human confirmation.
Known tools 3
discover-techunit-resourcesList TechUnit's machine-readable resources so an agent can fetch authoritative, first-party data.
Inferred read-onlyCONNECT 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.techunit-mcp]
url = "https://techunit.io/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"techunit-mcp": {
"type": "http",
"url": "https://techunit.io/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: techunit-mcp
Remote MCP URL: https://techunit.io/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": {
"techunit-mcp": {
"url": "https://techunit.io/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"techunit-mcp": {
"type": "http",
"url": "https://techunit.io/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "techunit-mcp",
"transport": "streamable-http",
"url": "https://techunit.io/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.