Developer Tools
yanib.dev
Retrieves and searches changelogs and release notes for software repositories.
ENDPOINT 1
https://www.yanib.dev/api/mcp
Known tools 0
No tool metadata was available in the registry cache.
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.yanib-dev]
url = "https://www.yanib.dev/api/mcp"
enabled = true
bearer_token_env_var = "MCP_BEARER_TOKEN"
Authentication is required. Replace the placeholder locally and never commit a secret.
Claude Code
.mcp.json
{
"mcpServers": {
"yanib-dev": {
"type": "http",
"url": "https://www.yanib.dev/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_BEARER_TOKEN"
}
}
}
}
Authentication is required. Replace the placeholder locally and never commit a secret.
Claude Desktop
Settings → Connectors → Add custom connector
Name: yanib-dev
Remote MCP URL: https://www.yanib.dev/api/mcp
Add the URL as a custom connector, then complete its supported authorization flow. Claude Desktop remote connectors are configured in the UI.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"yanib-dev": {
"url": "https://www.yanib.dev/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_BEARER_TOKEN"
}
}
}
}
Authentication is required. Replace the placeholder locally and never commit a secret.
Visual Studio Code
.vscode/mcp.json
{
"servers": {
"yanib-dev": {
"type": "http",
"url": "https://www.yanib.dev/api/mcp",
"headers": {
"Authorization": "Bearer ${input:mcp-token}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "mcp-token",
"description": "yanib-dev bearer token",
"password": true
}
]
}
Authentication is required. Replace the placeholder locally and never commit a secret.
Generic MCP
Client-specific MCP configuration
{
"name": "yanib-dev",
"transport": "streamable-http",
"url": "https://www.yanib.dev/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_BEARER_TOKEN"
}
}
Authentication is required. Replace the placeholder locally and never commit a secret.
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
ENDPOINT 2
https://www.yanib.dev/api/mcp/public
MCP server metadata
- Name
- yanib-public
- Version
- 1.0.0
Public, read-only changelog data for software projects tracked on Yanib. Use yanib_public_diff_releases before upgrading a dependency to see what changed between two versions (breaking changes are surfaced first). yanib_public_changelog lists a repo's recent releases; yanib_public_search finds releases by keyword. No authentication is required and only published changelogs are exposed.
Known tools 3
yanib_public_changelogReturn the most recent PUBLISHED releases (and their changelog entries) for a repo.
Inferred read-onlyyanib_public_diff_releasesReturn every changelog entry shipped between two version tags for a repo, grouped by change type with breaking-ish changes surfaced first.
Inferred read-onlyyanib_public_searchKeyword search across published release titles, summaries, and entries.
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.yanib-public]
url = "https://www.yanib.dev/api/mcp/public"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"yanib-public": {
"type": "http",
"url": "https://www.yanib.dev/api/mcp/public"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: yanib-public
Remote MCP URL: https://www.yanib.dev/api/mcp/public
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": {
"yanib-public": {
"url": "https://www.yanib.dev/api/mcp/public"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"yanib-public": {
"type": "http",
"url": "https://www.yanib.dev/api/mcp/public"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "yanib-public",
"transport": "streamable-http",
"url": "https://www.yanib.dev/api/mcp/public"
}
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.