Altimateguide Agent MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALTIMATEGUIDE_API_URL | No | Optional; overrides the API base. | https://altimateguide.com |
| ALTIMATEGUIDE_AGENT_TOKEN | Yes | 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. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_loginA | Email a one-time login code to begin browserless onboarding (POST /api/auth/request-code). Then read the code from the inbox and call complete_login. |
| complete_loginA | Exchange an email login code for an account API token and store it locally (POST /api/agent/token). The token is bound to that account; submissions are owned by it. |
| whoamiA | Confirm the configured token is live and report the account it belongs to (GET /api/agent/whoami). Distinguishes a missing token from a revoked/expired one. |
| list_categoriesA | List the valid category slugs (GET /api/agent/categories). Use these in submit_tool; anything that doesn't match goes in categorySuggestions. |
| check_duplicateA | Check whether a tool is already listed or already awaiting review (GET /api/agent/check) before submitting, so you don't burn a rate-limited write on a 409. |
| submit_toolA | Submit a tool to the Altimateguide directory for editorial review (POST /api/agent/submit). The listing is queued as pending and is never published automatically — an editor reviews it. Categories are optional; unknown/empty categories are recorded for the reviewer. Requires a token (run complete_login, or set ALTIMATEGUIDE_AGENT_TOKEN). |
| get_submissionA | Poll a submission's status (pending/approved/rejected), link tier, and whether a paid checkout has been verified (GET /api/agent/submissions/{id}). |
| upgrade_listingA | Choose how a listing you own earns a dofollow link (POST /api/agent/listing): sayabout, badge, or paid. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| submit_listing | Draft and submit a neutral listing for a tool. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Category slugs | The valid category slugs for submit_tool. |
| Editorial policy | How submissions are reviewed and what copy is accepted. |
TDQS
Scored across 8 tools
Each tool has a clearly distinct role: the two login steps are explicitly sequenced, whoami verifies the token, list_categories and check_duplicate are read-only preparations, and submit_tool/get_submission/upgrade_listing cover separate lifecycle stages. start_login vs complete_login could seem similar but the descriptions make the ordering and purpose unambiguous.
Most names follow a clean verb_noun snake_case pattern (start_login, complete_login, list_categories, check_duplicate, submit_tool, get_submission, upgrade_listing). The lone outlier is whoami, a conventional idiom but stylistically inconsistent with the rest.
Eight tools is well-scoped for a directory submission flow, with each tool earning its place across auth, lookup, submission, and monetization steps. No redundant or filler tools.
The surface covers the full agent workflow: authenticate, discover categories, avoid duplicates, submit, poll status, and choose link tier. Minor gaps exist (no way to edit or withdraw a pending submission), but the core lifecycle is fully served without dead ends.