Content Tools
mysaas.blog
Provides public access to blog posts, comments, and builder profiles.
ENDPOINT 1
https://mysaas.blog/mcp
Known tools 30
public_post_getRead one published post with content, SEO image, sources, tags and related SaaS.
Potential side effectspublic_saas_posts_listList visible SaaS entries for a builder and the published posts that mention them.
Inferred read-onlypost_getFetch one post by id, including translations, sources, tags and related SaaS.
Potential side effectspost_create_draftCreate a rich draft post with translations, images, SEO metadata, sources, tags and SaaS links.
Potential side effectspost_update_draftUpdate an existing draft post using the same rich payload shape as draft creation.
Potential side effectsCONNECT 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.mysaas-blog]
url = "https://mysaas.blog/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"mysaas-blog": {
"type": "http",
"url": "https://mysaas.blog/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: mysaas-blog
Remote MCP URL: https://mysaas.blog/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": {
"mysaas-blog": {
"url": "https://mysaas.blog/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"mysaas-blog": {
"type": "http",
"url": "https://mysaas.blog/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "mysaas-blog",
"transport": "streamable-http",
"url": "https://mysaas.blog/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for mysaas.blog was fetched 2026-08-04T02:33:25.797Z and is being refreshed.
mysaas.blog is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.