General Tools
infobytesnepal.com
Provides general-purpose tools through the Model Context Protocol.
ENDPOINT 1
https://www.infobytesnepal.com/api/mcp
MCP server metadata
- Name
- infobytes-nepal
- Version
- 1.0.0
Read-only access to everything Infobytes Nepal publishes. Start with search_site when the right tool is not obvious. Every result includes the public URL it came from — cite it.
Known tools 11
search_siteSearch everything Infobytes Nepal publishes — products, services, blog posts, landing pages, FAQs, open roles, and team members — and get back titles, summaries, and URLs.
Inferred read-onlyget_company_profileGet who Infobytes Nepal is, where they are based, how to contact them, which services and products they offer, and links to their machine-readable resources.
Inferred read-onlylist_servicesList the services Infobytes Nepal sells — web design and development, SEO, digital marketing, IT training, and graphic design — with what each includes and indicative timelines and prices.
Inferred read-onlylist_productsList the software products Infobytes Nepal builds and supports, such as Nidanyo, Serviol, Purseol, LeadRack, and Pravyo.
Inferred read-onlyget_productGet the full description of one product by its slug, as returned by list_products.
Inferred read-onlyget_blog_postGet one blog post by slug, including the entire body as markdown so it can be quoted or summarised.
Potential side effectslist_faqsGet answered questions about pricing, timelines, process, and support, with the indicative rupee ranges the company quotes publicly.
Inferred read-onlylist_open_rolesList the jobs and internships Infobytes Nepal is currently hiring for.
Inferred read-onlyget_open_roleGet the full description of one role by slug: responsibilities, requirements, compensation, and where to send an application.
Potential side effectslist_teamList the people at Infobytes Nepal, their roles, and what each of them specialises in.
Inferred read-onlyCONNECT 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.infobytes-nepal]
url = "https://www.infobytesnepal.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"infobytes-nepal": {
"type": "http",
"url": "https://www.infobytesnepal.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: infobytes-nepal
Remote MCP URL: https://www.infobytesnepal.com/api/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": {
"infobytes-nepal": {
"url": "https://www.infobytesnepal.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"infobytes-nepal": {
"type": "http",
"url": "https://www.infobytesnepal.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "infobytes-nepal",
"transport": "streamable-http",
"url": "https://www.infobytesnepal.com/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.