← univsense.com

INDIVIDUAL MCP TOOL

get_service

Full detail for one service: who it is for, scope, deliverables, the inputs UnivSense needs from the client, engagement type, timeline, price (scoped per engagement unless a figure is stated) and FAQ.

univsense.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://univsense.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_service and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

univsense.com

CONNECT 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.univsense]
url = "https://univsense.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "univsense": {
      "type": "http",
      "url": "https://univsense.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: univsense
Remote MCP URL: https://univsense.com/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": {
    "univsense": {
      "url": "https://univsense.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "univsense": {
      "type": "http",
      "url": "https://univsense.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "univsense",
  "transport": "streamable-http",
  "url": "https://univsense.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • list_services — List every UnivSense service (SEO, AI answer visibility, content, paid media, AI automation) with slug, name, one-line summary, engagement type and page URLs.
  • get_engagement_model — How engagements run (scope, build, run, hand over), how pricing works, response times, and what an agent may and may not do on a user's behalf.
  • get_contact — Email, phone numbers, addresses and the legal entity for UnivSense.
  • draft_scope_request — Build a prefilled scope-request email (a mailto: link plus the plain text) from the fields the user gave.