[MORSALIN]
MCP serverRead-only · no sign-in · public data

Ask your AI assistant about my services.

This site runs its own Model Context Protocol server. Connect it to Claude, ChatGPT, Cursor or VS Code, and your assistant can find the right service, quote starting prices, check availability and check your stack — from the same data as these pages.

https://morsalin.online/mcp
01Connect

Add it in a minute.

Claude (claude.ai, Claude Desktop)

Settings → Connectors → Add custom connector, then paste the URL.

https://morsalin.online/mcp

Claude Code

Run in a terminal:

claude mcp add --transport http morsalin https://morsalin.online/mcp

Cursor / VS Code

Add to your MCP config (mcp.json):

{
  "mcpServers": {
    "morsalin": { "url": "https://morsalin.online/mcp" }
  }
}

ChatGPT

Settings → Apps & Connectors → Advanced → Developer mode, then create a connector with the URL.

https://morsalin.online/mcp

Menu names change between app versions; if a path differs, look for “connectors” or “MCP servers” in settings.

02Tools

What your assistant can do.

find_service
Describe a need in plain words and get the matching services, with prices and links.
list_services
Every service, grouped by where the client is starting from.
get_service
One service in full: who it’s for, included and not, plans, process, FAQ.
availability_and_terms
Open client slots, next start date, founding spots, payment terms, guarantees.
check_stack
Paste a composer.json, package.json or Dockerfile; get versions that are past or near end of life.
eol_dates
Security-support end dates for runtimes, databases, servers, frameworks and operating systems.
case_studies
Past work with real numbers and links to the write-ups.

Try asking

  • “Does Morsalin do Laravel 10 to 13 upgrades, and what would it cost?”
  • “Here is my composer.json — what is out of support?”
  • “When does PostgreSQL 14 stop getting security fixes?”
  • “Is he available to start next month, and how do payments work?”
How it’s built

Want one for your SaaS?

This server is the same pattern I offer clients: read-only tools first, built on your existing data, with typed inputs, a public-data-only boundary and rate limits. Writes come later, with confirmation and scoped auth.

MCP server service →
  • › Streamable HTTP, stateless: a fresh server per request, no session to leak
  • › Seven read-only tools with typed, validated inputs
  • › Same data as the website, so answers never drift from it
  • › Rate-limited per visitor; nothing private is reachable
  • › Official TypeScript SDK, served by the site’s own Nuxt server
  • › Also in the page itself via WebMCP, for agents in Chrome: the same tools, plus the inquiry form, which the visitor still sends