Skip to content
skima.ai logo

skima.ai MCP server

Which MCP servers are skima.ai's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-08

← Back to skima.ai

Whose server it is
  • Addresshttps://skima.ai/api/mcpnot in the official registry: answered when asked

No entry in the official MCP registry names this server. It answered on skima.ai when the Atlas asked at the address servers are usually mounted on, so it is the vendor's own. Clients and catalogues that list servers from the registry do not show it.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools17
  • Server calls itselfskima-webmcp
  • Server version0.1.0
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 128 ms.

Should an agent connect itSkip it
  • Its tools do none of the product's use cases we checked: search existing ATS candidates against open job orders; verify candidate credentials before submitting them to clients; reach out to past candidates when a matching role opens.

Once connected

  • Parameters are untyped or undescribed in 9 of 17 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 7, the first on 2026-10-26
  • INITE MCP score67 of 100answers 100 · does the job 0 · definitions 75 · context 100 · connects 100
  • What an agent can do with it0 of 3 use cases
  • Answered100% of days7 of 7 daily checks
  • Median first answer303 ms
  • Space in an agent's context≈ 2,294 tokensthe definitions of all its tools (17), which an agent carries on every turn
  • Tool definitionsB · 75 of 100
  • Typed results0 of 17 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 9 of 17
  • Not saying whether it only reads or can destroy: 17 of 17

What an agent can do with it

  • cannot · search existing ATS candidates against open job orders
  • cannot · verify candidate credentials before submitting them to clients
  • cannot · reach out to past candidates when a matching role opens

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers17 tools · read 2026-10-26
  • get_available_slots

    List bookable Skima demo slots for a date range and IANA timezone. Window of up to 6 days per call; chain calls for wider searches. Each returned start_time is a value you can pass straight to book_demo as slot.available_slots.

  • book_demo

    Book a Skima product demo in one call: submit the lead form and reserve the chosen slot from get_available_slots. Caller must set terms_and_condition=true with explicit user consent.

  • get_pricing

    Return Skima pricing guidance. Skima pricing is custom-quoted; this tool returns a canned message plus links to schedule a demo and contact sales.

  • submit_pilot_lead

    Submit a 30-day Skima pilot lead. Captures prospect details (name, work email, company, company size, current ATS, top hiring priorities, recruiter count, preferred start window). Use only with explicit user consent.

  • start_free_trial

    Start a 14-day Skima free trial. Returns the canonical signup URL and next steps so an agent can deep-link the user. Idempotent, no backend write.

  • subscribe_newsletter

    Subscribe an email to the Skima newsletter. Captures only the email address. Use only with explicit user consent.

  • list_integrations

    List the ATS/HRIS/CRM integration partners Skima ships natively. Filter by name or type. Use to answer 'does Skima work with [system]?'.

  • list_glossary

    List Skima glossary entries (product + recruiting industry terms). Pass title to filter. Without arguments returns the full alphabetised index.

  • list_evaluations

    List Skima evaluation articles (assessments, candidate scorecards, role-specific evaluation guides). Paginated.

  • list_blog

    List Skima blog posts. Optionally filter by category slug or title search. Useful for answering 'has Skima written about X?'.

  • list_product_updates

    List Skima product release notes. Optionally filter by category, month, year. Use to answer 'what shipped recently?'.

  • get_product_update

    Fetch a single product release note by slug. Returns full content including key takeaways and tabs.

  • get_competitor_comparison

    Fetch the structured Skima vs [competitor] comparison page. Returns hero, feature matrix, and Skima differentiators. Pass the full CMS slug, e.g. 'skima-ai-vs-greenhouse', 'skima-ai-vs-lever'.

  • list_customer_stories

    List Skima customer stories / case studies. Use as social proof when a prospect asks who already uses Skima.

  • get_customer_story

    Fetch a single Skima customer story by slug. Returns summary + URL to the full case study page.

  • list_products

    List Skima products with name, slug, URL, and one-line summary. Use to give an agent a clean map of what Skima ships.

  • list_solutions

    List Skima solutions by axis. axis='industry' returns industry verticals (finance, healthcare, ...). axis='size' returns company-size segments (enterprise, ...).

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "skima": {
      "type": "http",
      "url": "https://skima.ai/api/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http skima https://skima.ai/api/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://skima.ai/api/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.