Detect frontend-backend contract drift and find frontend calls to missing backend APIs.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "tieline" MCP server from askskill: Run: claude mcp add 'io-github-nugehs-tieline' -- npx -y @nugehs/tieline
Use tieline to check whether the API calls in the current frontend code match the backend-exposed interfaces. List all endpoints called by the frontend but not provided by the backend, grouped by file path.
A contract drift report with missing APIs, affected files, and issue locations.
Run tieline to check contract drift for this change set. If the frontend calls backend APIs that do not exist, summarize the errors in a format suitable for CI logs.
CI-friendly validation results clearly showing failure reasons and problematic endpoints.
Use tieline to analyze frontend-backend interface mismatches. Identify where request paths, methods, or parameter contracts differ from backend-exposed definitions, and organize them into a troubleshooting checklist.
A troubleshooting checklist that helps the team quickly locate root causes of API mismatches.
Analyze Solidity contracts in your editor to catch security and quality issues.
Check EVM contract and token risks before interaction.
Query TypeScript dependency graphs to find the minimal files for review or debugging.
Probe live APIs and explain failures with root causes and confidence.
Statically scan MCP server configs for safety and setup issues before running.
Let AI inspect DOM, console, and network to debug web apps.