Pakish.NET Hosting MCP

Compare published shared hosting plans and renewal prices, then prepare a nonbinding quotation after customer consent.

Hosted MCP Server

npx add-mcp 'https://pakish.net/api/agent-commerce/mcp'

Installs into Claude Code, Codex, Cursor and more

Documentation

Clear hosting information for your AI assistant.

Compare plans, read published charges and understand renewal terms. These public resources work without a login and help you prepare a purchase for your customer to review.

Published prices require checkout confirmation

Amounts below are indicative website catalog charges, not a live quote or reservation. Confirm promotion eligibility, currency, setup fees, taxes and the final total at checkout. Unknown charges are represented as null in the catalog; they are not zero.

The customer must review the selected plan, billing term and renewal terms before purchasing. Optional inquiry and private estimate requests are available when the pilot is enabled. They do not accept quotes, create orders, charge payments or provision services.

Compare shared hosting plans

Naya Josh

Ideal for personal projects and blogs.

1 website · 10 GB storage

pakish.shared-hosting.naya-josh

Naya Jazba

Power and scale for growing businesses.

2 websites · 50 GB storage

pakish.shared-hosting.naya-jazba

Naya Junoon

Maximum performance for mission-critical sites.

5 websites · 100 GB storage

pakish.shared-hosting.naya-junoon

PlanInitial termPublished first chargePublished renewalCustomer review
Naya Josh90-day trialPKR 0PKR 3,000 / 3 monthsReview at checkout
Naya Josh12 monthsPKR 8,111PKR 11,111 / 12 monthsReview at checkout
Naya Josh36 monthsPKR 14,280PKR 17,280 / 36 monthsReview at checkout
Naya Jazba90-day trialPKR 0PKR 4,000 / 3 monthsReview at checkout
Naya Jazba12 monthsPKR 12,666PKR 16,666 / 12 monthsReview at checkout
Naya Jazba36 monthsPKR 29,332PKR 33,332 / 36 monthsReview at checkout
Naya Junoon90-day trialPKR 0PKR 4,500 / 3 monthsReview at checkout
Naya Junoon12 monthsPKR 13,350PKR 17,850 / 12 monthsReview at checkout
Naya Junoon36 monthsPKR 31,200PKR 35,700 / 36 monthsReview at checkout

How an assistant should use this catalog

  1. Ask about website count, storage needs, budget and preferred billing term. Clarify missing requirements before recommending a plan.
  2. Fetch the catalog and compare the full first-term charge with the renewal charge. Amounts use integer minor units: divide by 100 to display PKR.
  3. Explain unknown charges and eligibility conditions. Do not invent discounts, capacity guarantees or included domain terms.
  4. Present the matching checkout link to the customer. Opening it can change their cart; let the customer review and proceed.
  5. Submit a consented hosting inquiry when the pilot is available, or use the sales contact page. Keep the private review link confidential. On the review page, ask about hosting options in English, Roman Urdu or Urdu. The optional pilot allows three catalog-backed replies; custom prices need sales approval.
curl https://pakish.net/agent-catalog.json

The current checkout remains in place during the LuraFlow migration. Product identifiers are stable across that transition.

Replies and unsent email drafts have separate rollout controls. No email is sent or inbox monitored by this website flow. Email documents require a human to verify the recipient, original thread and current estimate before sending. Ask for a human to pause automated replies.

Connect an MCP or A2A client

Use the MCP Streamable HTTP endpoint at /api/agent-commerce/mcp, or discover the A2A 1.0 JSON-RPC interface through the Agent Card. MCP supports the current 2026-07-28 protocol and the SDK's stateless legacy handshake compatibility. Both adapters share the existing inquiry and quotation engine.

Read the operation schemas and connection contract. Public catalog requests need no account. Ask for explicit consent before creating an inquiry. Keep its returned capability confidential and provide it only in subsequent operation arguments. An inquiry capability gives access to that inquiry alone and does not authenticate a customer account.

A2A returns synchronous Messages. Send a structured data part containing tool and arguments; use a UUID messageId as the retry key. Private text follow-ups use the inquiry UUID as contextId and its capability in message metadata. There are no A2A Task resources, streaming, push callbacks, payments or provisioning operations. Unsupported requirements and exhausted reply budgets go to sales review.