Altimateguide Agent MCP Server
Use the Altimateguide MCP server to authenticate, submit/track a tool listing, and manage its upgrade path; the README also documents no-account research tools.
Authenticate via email one-time code or configured token, and check account/token status.
List valid category slugs and preflight duplicate name/URL checks.
Submit a tool for editorial review with optional categories, features, pros/cons, pricing/free-plan/trial, proof path, and idempotent replay/resubmit controls.
Poll submission status, link tier, and paid-checkout verification.
Upgrade an owned listing via sayabout, badge, or paid checkout; dofollow only after server-side payment verification.
Per README (not in supplied schema): search tools, get tool profiles, compare tools, find alternatives, and list live deals without an account.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Altimateguide Agent MCP Server Submit my tool Acme Analytics to Altimateguide for review."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Altimateguide Agent MCP Server
The MCP server for Altimateguide, an independent software directory. It has two halves:
Research — no account. Search tool profiles, compare two tools, find alternatives, and list live deals. Every result carries its canonical altimateguide.com URL.
Submission — with an account token. Submit a tool to the directory for editorial review, add a time-boxed deal, and upgrade the listing. The paid listing is the fastest route: a one-time fee, reviewed within 2 business days, with no badge or wall to install.
The same server is available two ways: hosted over streamable HTTP at
https://altimateguide.com/api/mcp, or locally over stdio via npx. One tool
surface, one code path (src/server.ts).
Scope: this server only talks to the public Altimateguide HTTP API. It holds no database credentials and grants no access beyond submitting/owning listings. Nothing is published without an editor reviewing it, and no submission can self-grant a dofollow link — a paid listing only becomes a dofollow candidate once its payment is verified server-side. Paid and verified listings are reviewed in 2–7 business days; free no-verification listings stay nofollow and are reviewed within 30 days.
Fastest route to dofollow: submit the tool (with proof: "none" or omitted),
then call upgrade_listing with path: "paid". It returns a Dodo checkout URL
for the human to complete, and the link becomes dofollow once the payment is
verified server-side. Read the current price and the recommended path from the
altimateguide://listing-paths resource.
Tools
Research (no account needed)
Tool | What it does |
| Search published tools by keyword, category or free plan ( |
| Read one profile: pricing, free plan/trial, pros, cons, features, rating ( |
| Compare two tools, with the canonical |
| Curated alternatives page first, then same-category tools ( |
| Live lifetime deals, sales and launch offers ( |
Submission (account token)
Tool | What it does |
| Email a one-time login code ( |
| Exchange the code for an account API token and store it ( |
| Begin an AgentID sign-in with no email inbox — returns an |
| Poll the AgentID sign-in and store the account token once it completes ( |
| Report whether a token is configured locally. |
| The valid category slugs ( |
| Preflight a name/URL against published tools + the pending queue ( |
| Submit a listing for editorial review ( |
| Submit a time-boxed deal — lifetime deal, sale, or launch offer ( |
| Poll a submission's status ( |
| Edit the facts of a listing you own — only the fields you pass change ( |
| Visits/upvotes/saves/reviews for your listings, with 7- and 30-day windows ( |
| Choose paid (fastest — returns a checkout URL), sayabout, or badge for a listing you own ( |
It also exposes the category list, the editorial policy, and the listing
paths/pricing (with the recommended path) as resources, a submit_listing
prompt, and category-slug completions. Server instructions summarise
the workflow for the model.
submit_tool parameters
name(string, required) — tool nameurl(string, required) — canonical http(s) URLdescription(string, optional) — neutral copy, min 20 charscategories(array, optional) — slugs fromlist_categoriescategorySuggestions(array, optional) — free-text hints when none fit (recorded for the reviewer)features(array, optional) —{ label, description? }itemspros/cons(array, optional),pricing/freePlan/freeTrial(optional)proof(string, optional) —none(default; free, no verification, nofollow) |sayabout|badgeverificationUrl(string) — required forsayabout/badgeexternalId(string, optional) — your id for idempotent replays (derived from the URL when omitted)source(string, optional) — origin id (defaultagent:mcp)resubmit(boolean, optional) — settrueto send a fresh copy after a previous submission for this URL was rejected (mints a new idempotency key instead of replaying the rejected row)
Categories are optional. An unknown or missing category never fails the
submission — it is recorded for the reviewer, exactly like the site's feed
pipeline. Paid (dofollow) listings are not submitted here; use
upgrade_listing with path: "paid", which returns a Dodo checkout URL whose
payment is verified server-side.
submit_deal parameters
A deal is a time-boxed offer attached to a listing — a lifetime deal, a sale, or a launch price. It is separate from the listing itself: it never changes the link tier, and it only appears on https://altimateguide.com/deals once approved.
name(string, required) — product nameurl(string, required) — canonical product URL (matched to a listing by domain)dealUrl(string, required) — the page documenting the offer; review verifies the price and dates against itprice(number, required) — current offer price in USDkind(string, required) —ltd|sale|launchbilling(string, optional) —one-time(default) |month|yearwasPrice(number, optional) — pre-deal price, shown struck throughendsAt(string, optional) —YYYY-MM-DD; omit it for an open-ended offertiers(array, optional) —{ name, codes? }itemsdescription(string, optional) — "what's included", shown on the deals hubcategories(array, optional) — slugs for an unlisted productpaymentRef(string, optional) — a paid listing's payment ref → priority laneexternalId(string, optional) — idempotency key (derived from the URLs when omitted)source(string, optional) — origin id (defaultagent:mcp)
Deal review: free within 7 calendar days, priority within 2 business days
with paymentRef. The response carries review_eta, needs_listing (true when
the product is not listed yet) and link_tier: "unchanged". Open-ended offers
(no endsAt) stay live while their last verification is under 30 days old.
Full request/response contract: https://altimateguide.com/openapi.json.
Related MCP server: stendium-mcp
Review times
Turnaround and link tier both come from proof:
| Link | Review |
| dofollow | within 2 business days |
| dofollow | within 2 business days |
| dofollow | 5–7 business days |
| nofollow | within 30 days |
none is the free no-verification lane — the same one a human can request at
https://altimateguide.com/free-listing. Paid and verified submissions are
reviewed ahead of free no-verification ones. Both the submit_tool response and
get_submission include an upgrade hint while a submission is in the free
no-verification lane (still nofollow):
recommended: "paid" (with the current price_usd) plus the free sayabout /
badge alternatives. Surface that to the user before they settle for nofollow.
The response also carries review_eta (unit is calendar_days for none,
business_days otherwise).
Configuration
ALTIMATEGUIDE_AGENT_TOKEN— optional. An account API token (create at https://altimateguide.com/account, or mint one with thecomplete_logintool). When set, it takes precedence over the stored token.ALTIMATEGUIDE_API_URL— optional; overrides the API base (defaulthttps://altimateguide.com).ALTIMATEGUIDE_CONFIG_DIR— optional; wherecomplete_loginstores the token (default~/.config/altimateguide).
Install & use
npx -y altimateguide-agent-mcp # run directly (stdio)Remote (streamable HTTP)
The hosted endpoint needs no install and no token for the research tools:
https://altimateguide.com/api/mcp{
"mcpServers": {
"altimateguide": {
"type": "http",
"url": "https://altimateguide.com/api/mcp"
}
}
}Per-client setup (Claude Code, Codex, Gemini CLI, VS Code, Cursor, Claude, ChatGPT): https://altimateguide.com/mcp/install.
The hosted endpoint exposes the research tools only (search_tools, get_tool,
compare_tools, find_alternatives, list_deals, list_categories). Submission
tools read a token from the server process — on a shared host that would mean acting
as the deployment's account — so they stay on the local stdio server until OAuth
gives each caller its own credential. createServer({ hosted: true }) enforces this.
The transport is stateless — no session id, JSON responses instead of SSE — so it runs behind serverless functions without sticky routing.
To run the HTTP transport yourself:
npm run dev:http # tsx, :3000
npm run build && npm run serveOr from a local checkout:
npm install
npm run build # tsc -> dist/
npm run dev # stdio server via tsx (for local testing)Claude Desktop / other MCP clients
{
"mcpServers": {
"altimateguide": {
"command": "npx",
"args": ["-y", "altimateguide-agent-mcp"]
}
}
}The token can be supplied via env.ALTIMATEGUIDE_AGENT_TOKEN, or obtained at
runtime by calling start_login + complete_login (the agent needs access to
the mailbox it registers).
(From a local checkout, use "command": "node" and
"args": ["/absolute/path/to/dist/index.js"].)
Development
npm run check # tsc --noEmit
npm run lint # eslint
npm test # vitest
npm run build # tsc -> dist/
npm run bundle # build a .mcpb (Smithery / Claude Desktop)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/
│ ├── server.ts # createServer(): tools, resources, prompts, completions (one surface)
│ ├── index.ts # stdio entry (the npx bin)
│ ├── http.ts # streamable HTTP entries: web-standard + node
│ ├── read.ts # public read tools (no auth)
│ ├── api.ts # shared fetch client (timeout, retry, error mapping)
│ ├── auth.ts # start_login / complete_login / whoami
│ ├── categories.ts # list_categories + matching
│ ├── submit.ts # submit_tool
│ ├── deal.ts # submit_deal
│ ├── listing.ts # check_duplicate / get_submission / upgrade_listing
│ ├── update.ts # update_listing
│ ├── stats.ts # get_listing_stats
│ ├── credentials.ts # token storage (~/.config/altimateguide)
│ ├── schema.ts # zod -> JSON Schema helper
│ └── version.ts # package version
├── test/ # vitest
├── server.json # MCP Registry manifest
├── mcpb/manifest.json # .mcpb bundle manifest
├── package.json
└── tsconfig.jsonSecurity & permissions
This server is a thin, local client for the public Altimateguide HTTP API — no database access, no subprocess, no background work. The capabilities below are the entire surface (the same surface a supply-chain scanner reports):
Network — outbound HTTPS only, to the base in
ALTIMATEGUIDE_API_URL(defaulthttps://altimateguide.com). The endpoints it calls are exactly the ones in Tools (/api/public/…,/api/auth/…,/api/agent/…,/openapi.json). No telemetry and no third-party calls.Environment variables — reads
ALTIMATEGUIDE_AGENT_TOKEN,ALTIMATEGUIDE_API_URL, andALTIMATEGUIDE_CONFIG_DIR. Nothing is written back.Filesystem — one file: the account token at
${ALTIMATEGUIDE_CONFIG_DIR:-~/.config/altimateguide}/credentials.json, created with mode0600. No other paths are touched.No subprocess, no database — it never spawns a process and holds no database credentials.
Credentials: an ALTIMATEGUIDE_AGENT_TOKEN environment variable always takes
precedence over the stored file, so CI-style setups can inject a token without
writing to disk.
Nothing is published without editorial review, and a paid listing only becomes a dofollow candidate once its payment is verified server-side.
License
MIT — see LICENSE.
Available Tools
8 toolscheck_duplicateARead-only
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.
Inputs: url, name.
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.
Inputs: code (required), email (required), name.
get_submissionARead-only
Poll a submission's status (pending/approved/rejected), link tier, and whether a paid checkout has been verified (GET /api/agent/submissions/{id}).
Inputs: id (required).
list_categoriesARead-only
List the valid category slugs (GET /api/agent/categories). Use these in submit_tool; anything that doesn't match goes in categorySuggestions.
Inputs: no named parameters.
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.
Inputs: email (required).
submit_toolAIdempotent
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).
Inputs: url (required), name (required), cons, pros, +12 more.
upgrade_listingA
Choose how a listing you own earns a dofollow link (POST /api/agent/listing): sayabout, badge, or paid. paid returns a Dodo checkout URL whose metadata carries the submission id; the payment is verified server-side by the Dodo webhook. Nothing publishes or self-grants dofollow here.
Inputs: path (required), slug, submissionId, verificationUrl.
whoamiARead-only
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.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Independent directory of agentic AI tools — search, compare & recommend via MCP. Read-only.
Tool shop for AI agents: ready x402 tools to call or own, or order one built for $1. Free tries.
A registry of AI agent tools — MCP servers, APIs, CLIs, SDKs — kept current by automated ingestion.
The marketplace where agents don't just use tools — they build, publish, and compose new ones.
Related MCP Servers
- AlicenseNot gradedqualityFmaintenanceEnables AI agents to manage App Store Connect apps, including registering bundle IDs, uploading metadata and screenshots, setting age ratings, managing TestFlight groups and testers, and submitting apps for review.MIT

stendium-mcpofficial
AlicenseNot gradedqualityDmaintenanceEnables any MCP-compatible agent to publish tool cards to Stendium, a portfolio showcase, after user confirmation.10 npmMIT- AlicenseAqualityDmaintenanceEnables AI agents to search, score, review, and submit tools from the SkillsIndex directory of 11,000+ AI agent tools.994 npmMIT
- AlicenseAqualityCmaintenanceEnables agents to call typed code-review and content-moderation decision tools, returning structured verdicts, probabilities, and confidence-gated actions.2MIT