Altimateguide

io.github.imharikumaranv1.0.1Updated Oct 3, 2026

Submit a tool to the Altimateguide directory for editorial review.

VerifiedSTDIODesktop onlyBusiness & CommerceProductivity & Workflow

Overview

AI-generated overview

Lets an assistant submit a tool listing to the Altimateguide directory for editorial review.

What it does
Exposes a single tool, submit_tool, which posts a listing to the public Altimateguide HTTP API endpoint for agent submissions. The submission includes a name, canonical URL, category slugs, and optional description, features, proof type, verification URL, payment reference, and external ID. Submissions land in a pending state and are reviewed by a human editor; nothing is published automatically. The response returns a submission ID, status, proof, and link tier.
When to use it
Use it when you want an assistant to add a tool or product to the Altimateguide directory without filling in the web form by hand, or to replay submissions idempotently using your own external ID. It is a narrow, single-purpose server, so it is only worth adding if you actually submit listings there.
Requirements
Runs locally over stdio, typically via npx altimateguide-agent-mcp, so Node.js is needed. Requires an account API token in the environment variable ALTIMATEGUIDE_AGENT_TOKEN, created from the account's Agent & API access page. The optional ALTIMATEGUIDE_API_URL overrides the API base. Network access to the Altimateguide API is required.
Before you install
The server asks for ALTIMATEGUIDE_AGENT_TOKEN, a per-account secret that identifies the submitter; anyone holding it can submit as that account, so keep it out of shared configs and revoke it if exposed. Submissions write data to a third-party service and are sent to Altimateguide's servers. The paid proof option requires a paymentRef, so confirm any payment or fee before using it. Submissions are queued for human review rather than published automatically.

Installation

In SourceWeft

  1. Open Altimateguide in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Altimateguide Agent MCP Server

[smithery badge]

A small MCP server that lets an AI agent submit a tool to the Altimateguide directory for editorial review. It exposes exactly one tool: submit_tool.

Scope: this server only talks to the public Altimateguide HTTP API (POST /api/agent/submit). It holds no database credentials and grants no access to anything beyond submitting a listing — which is always queued for human review and never published automatically.

The tool: submit_tool

Submits a listing for editorial review. The submission lands as pending; an editor reviews it.

  • Parameters
    • name (string, required) — tool name
    • url (string, required) — canonical http(s) URL
    • categories (array, required) — one or more category slugs
    • description (string, optional) — neutral copy, min 20 chars
    • features (array, optional) — { label, description? } items
    • proof (string, optional) — none (default) | sayabout | badge | paid
    • verificationUrl (string) — required for sayabout/badge
    • paymentRef (string) — required for paid
    • externalId (string, optional) — your own id, for idempotent replays
    • source (string, optional) — origin id (default agent:mcp)
  • Returns — the API response: submission_id, status, proof, link_tier.

Full request/response contract: https://altimateguide.com/openapi.json.

Configuration

  • ALTIMATEGUIDE_AGENT_TOKEN — required. A per-account API token. Create one at https://altimateguide.com/account (Agent & API access); it is bound to that account, shows as the submitter, and can be revoked.
  • ALTIMATEGUIDE_API_URL — optional; overrides the API base (default https://altimateguide.com).

Install & use

bash
npx -y altimateguide-agent-mcp        # run directly (stdio)

Or from a local checkout:

bash
npm installnpm run build      # tsc -> dist/npm run dev        # stdio server via tsx (for local testing)

Claude Desktop / other MCP clients

json
{  "mcpServers": {    "altimateguide": {      "command": "npx",      "args": ["-y", "altimateguide-agent-mcp"],      "env": {        "ALTIMATEGUIDE_AGENT_TOKEN": "atg_..."      }    }  }}

(From a local checkout, use "command": "node" and "args": ["/absolute/path/to/dist/index.js"].)

Registries

Listed via server.json (the MCP Registry manifest). It is a standard stdio server, so it also works with the community directories (Glama, PulseMCP, mcp.so, mcp.directory).

Project structure

.├── src/index.ts     # stdio MCP server + the submit_tool handler├── server.json      # MCP Registry manifest├── package.json├── tsconfig.json└── README.md

License

MIT — see LICENSE.

Source: README.md at commit dbf590b

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.1LatestOct 3, 2026