MLP Tax Computation Engine
REMOTE · API.LUCASANDERSEN.AI · SCANNED OCT 6
Deterministic MLP tax engine with IRS citations. 6 tools: basis, §751, estate, projections.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability55
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3033 tokens (~505/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 57% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the MLP Tax Computation Engine MCP server?
MLP Tax Computation Engine is a hosted endpoint at https://api.lucasandersen.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.lucasandersen.ai
claude mcp add --transport http ai-lucasandersen-mlp-tax 'https://api.lucasandersen.ai/mcp'
{
"mcpServers": {
"ai-lucasandersen-mlp-tax": {
"url": "https://api.lucasandersen.ai/mcp"
}
}
} {
"servers": {
"ai-lucasandersen-mlp-tax": {
"type": "http",
"url": "https://api.lucasandersen.ai/mcp"
}
}
} [mcp_servers.ai-lucasandersen-mlp-tax] url = "https://api.lucasandersen.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-lucasandersen-mlp-tax": {
"type": "remote",
"url": "https://api.lucasandersen.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-lucasandersen-mlp-tax --url 'https://api.lucasandersen.ai/mcp' --transport streamable-http
mcp_servers:
ai-lucasandersen-mlp-tax:
url: "https://api.lucasandersen.ai/mcp" {
"McpServers": {
"ai-lucasandersen-mlp-tax": {
"Transport": "http",
"Url": "https://api.lucasandersen.ai/mcp"
}
}
} assistant mcp add ai-lucasandersen-mlp-tax -t streamable-http -u 'https://api.lucasandersen.ai/mcp'
{
"mcpServers": {
"ai-lucasandersen-mlp-tax": {
"type": "http",
"url": "https://api.lucasandersen.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 −1
- Stability: pass → 0.87 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 19 Aug 26 0
- Tool “k1_basis_compute” rewrote its description, which is the text the model reads security
- Tool “k1_basis_multi_year” rewrote its description, which is the text the model reads security
- Tool “mlp_estate_planning” rewrote its description, which is the text the model reads security
- Tool “mlp_sell_vs_hold” rewrote its description, which is the text the model reads security
- Schema quality: good → excellent functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Oct 2026 · Probed https://api.lucasandersen.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lucasandersen.ai | CN=WE1,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 6e0618c002b5064913db5c3b5cc6cd6f |
| SANs: lucasandersen.ai, api.lucasandersen.ai, *.api.lucasandersen.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.lucasandersen.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| lucasandersen.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.lucasandersen.ai/mcp | Verified | 200 | |
| http (plaintext) | http://api.lucasandersen.ai/mcp | HTTPS enforced | 301 | https://api.lucasandersen.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
k1_basis_compute ~646
Computes adjusted partner basis from a single year of Schedule K-1 data using the IRS Partner's Basis Worksheet methodology (Lines 1-14), per IRC §705 (basis computation), §722 (initial basis), §731(a)(1) (gain on distribution exceeding basis), §733 (basis reduction), §752 (liability share allocation), §704(d) (loss limitation and suspended-loss carryforward), and §199A (QBI deduction). Returns the ending adjusted basis, every worksheet line value, any §731 gain triggered when distributions exceed basis, and §704(d) suspended losses carried forward. Use when: User holds direct MLP units (EPD, ET, MPLX, WES, PAA, NRP, USAC, SUN, or similar publicly traded midstream partnerships) and has structured K-1 box values for one tax year — Box 1 ordinary income, Box 19A cash distributions, Item K liability change, optionally Box 5 interest income, Box 11 §179 deduction, Box 13W §199A QBI amount. Single tax year, single lot. Don't use for: 1099-DIV ETFs (AMLP, MLPX, AMZA — these use RIC structure, no K-1, different tax regime — use a standard cost-basis calculator instead). Multi-year basis carryforward across consecutive K-1s — use k1_basis_multi_year. General partnership interests outside publicly traded MLPs (different §1402 self-employment treatment). Limitations: Single tax year only — for multi-year basis tracking with §731 gain detection across years, use k1_basis_multi_year. Single-lot only — for multi-lot allocation and optimal sell ordering, see lucasandersen.ai. Federal-level only — does not include state basis adjustments. Full multi-year basis reconstruction with a CPA-ready workpaper is available at https://lucasandersen.ai/private-partnership-k1-basis?src=mcp&tool=k1_basis_compute&surface=description. Maintained by Lucas Andersen, MS Finance, with direct positions in major midstream MLPs. Methodology auditable at lucasandersen.ai/methodology.
| Name | Type | Req | Description |
|---|---|---|---|
| box1 | number | yes | K-1 Box 1: ordinary business income (loss) |
| box11 | number | – | K-1 Box 11: §179 / other deductions |
| box13w | number | – | K-1 Box 13W: §199A QBI amount |
| box19a | number | yes | K-1 Box 19A: cash distributions |
| box2 | number | – | K-1 Box 2: net rental income |
| box5 | number | – | K-1 Box 5: interest income |
| liability_decrease | number | – | §752(b) liability decrease in USD |
| liability_increase | number | – | §752(a) liability increase in USD |
| prior_basis | number | yes | Beginning-of-year adjusted basis in USD |
| tax_bracket | number | – | – |
| ticker | string | yes | – |
| units | number | yes | – |
No output schema declared.
No examples provided.
k1_basis_multi_year ~558
Computes a running adjusted partner basis across multiple years of Schedule K-1 data, per IRC §705 (basis computation), §731(a)(1) (gain on distributions exceeding basis), §751(a) (accumulated ordinary recapture), §752 (liability share allocation across years), §704(d) (suspended-loss carryforward), and §1014(a) (step-up if death today). Returns year-by-year basis trajectory, accumulated §751 recapture estimate, projected zero-basis year, §1014 step-up value if death today, and the broker-basis gap — the dollar amount by which a typical 1099-B understates true IRS-adjusted basis. Use when: User holds a direct MLP position (EPD, ET, MPLX, WES, PAA, NRP, USAC, SUN) across multiple consecutive tax years, has K-1s for those years, and wants to track adjusted basis year over year, identify the zero-basis year, quantify the gap between broker-reported basis and true IRS basis, or project §1014 step-up value if death occurred today. Don't use for: Single-year basis worksheet from one K-1 — use k1_basis_compute. Long-horizon forward projection from default assumptions when no actual K-1s are in hand — use mlp_projection. 1099-DIV ETFs (AMLP, MLPX, AMZA — RIC structure, no K-1, no basis-erosion mechanism; use a standard cost-basis calculator). Multi-position portfolio basis tracking — this tool handles one position per call. Limitations: Single position, single lot — for multi-lot or multi-position basis tracking with optimal sell ordering, see lucasandersen.ai. Federal-level only — does not include state-level basis adjustments. Accumulated §751 recapture is estimated across years; actual depends on the partnership's hot-asset disposition schedule and any year-specific §751(b) events. Full multi-year basis reconstruction with a CPA-ready workpaper is available at https://lucasandersen.ai/private-partnership-k1-basis?src=mcp&tool=k1_basis_multi_year&surface=description. Maintained by Lucas Andersen, MS Finance, with direct positions in major midstream MLPs. Methodology…
| Name | Type | Req | Description |
|---|---|---|---|
| k1_years | array | yes | Array of annual K-1 data, one per year held (max 50) |
| purchase_price | number | yes | – |
| purchase_year | number | – | – |
| tax_bracket | number | – | – |
| ticker | string | yes | – |
| units | number | yes | – |
No output schema declared.
No examples provided.
mlp_estate_planning ~555
Computes §1014 stepped-up basis and estate-planning analysis for one or more direct MLP positions held until death, per IRC §1014(a) (basis at death), §1014(b)(6) (community-property double step-up), §751(a) (ordinary recapture eliminated at death), §731 (distributions), and §705 (basis). Returns total deferred federal tax eliminated, §751 ordinary recapture eliminated, per-beneficiary inheritance split, community-property double-step-up amount when applicable, and the dollar advantage of holding to death versus selling today. Use when: User has one or more direct MLP positions (EPD, ET, MPLX, WES, PAA, NRP, USAC, SUN) and wants to quantify the §1014 step-up benefit for estate planning, compare holding to death versus selling now across a portfolio, model community-property double step-up for spouses in CA/TX/WA/etc., or compute per-beneficiary inheritance values across multiple heirs. Don't use for: Trust-based estate strategies (revocable trusts preserve §1014; irrevocable trusts and IDGTs typically destroy it — this tool models direct holdings only). Single-position long-horizon tax projection — use mlp_projection. Single-position sell-now-versus-hold-to-death break-even — use mlp_sell_vs_hold. 1099-DIV ETFs (AMLP, MLPX, AMZA — RIC structure receives §1014 step-up but has no §751 to eliminate because no K-1; the analysis is materially different). Limitations: Direct unit holdings only — does not model trust, IDGT, FLP, or charitable structures (these can destroy the §1014 benefit; for guidance on trust selection, see lucasandersen.ai). Federal-level only — does not include state estate tax. §751 recapture eliminated at death is estimated; exact figure depends on the partnership's actual hot-asset disposition schedule. A year-by-year basis workpaper for this position is available at https://lucasandersen.ai/tax/k1-basis-tracker?src=mcp&tool=mlp_estate_planning&surface=description. Maintained by Lucas Andersen, MS Finance, with direct positions in major midstr…
| Name | Type | Req | Description |
|---|---|---|---|
| beneficiaries | number | – | Number of beneficiaries (default 1, max 20) |
| community_property | boolean | – | Whether positions are in a community property state (doubles step-up) |
| positions | array | yes | Array of MLP positions to analyze (max 20) |
| tax_bracket | number | – | – |
No output schema declared.
No examples provided.
mlp_info ~217
Returns reference data for a supported MLP ticker — current cash distribution per unit, distribution growth CAGR, default return-of-capital percentage, distribution coverage ratio, K-1 entity count, operating-state count, and last-verified date. Use when: User wants to look up baseline characteristics of an MLP before modeling — e.g., comparing distribution coverage across partnerships, checking how many K-1 entities a holding generates for tax-prep complexity, or seeing the operating-state count for state-tax filing-burden estimation. Don't use for: Tax computation. Use mlp_projection (long-horizon modeling), mlp_estate_planning (estate analysis), mlp_sell_vs_hold (break-even sell price), or k1_basis_compute / k1_basis_multi_year (computing basis from actual K-1 data). Note: This tool returns reference data only — no IRC citations apply, no methodology disclosure attached. For computation, use the modeling tools above. Maintained by Lucas Andersen, MS Finance.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | – |
No output schema declared.
No examples provided.
mlp_projection ~512
Computes a multi-year tax projection for a publicly traded MLP position, applying the IRS Partner's Basis Worksheet methodology (Lines 1-14) per IRC §705 (basis computation), §731(a) (distributions exceeding basis), §733 (basis reduction), §751 (hot asset recapture), §752 (liability allocation), §1014 (stepped-up basis at death), and §199A (QBI deduction). Returns year-by-year basis erosion, §751 accumulation, annual federal tax, terminal FMV, §1014 step-up value at death, and the break-even sell price. Use when: User holds direct units of a midstream MLP (EPD, ET, MPLX, WES, PAA, NRP, USAC, SUN) and wants to model long-term tax outcomes — when basis reaches zero, total tax paid over the hold horizon, deferred tax eliminated by §1014 step-up at death, or the unit price at which selling matches holding through inheritance. Single position, single lot. Don't use for: 1099-DIV ETFs (AMLP, MLPX, AMZA — these use RIC structure, pay corporate-level tax, and issue 1099-DIV instead of K-1; use a standard cost-basis calculator instead). Multi-position estate analysis — use mlp_estate_planning. Computing basis from actual K-1 data the user has in hand — use k1_basis_compute (single year) or k1_basis_multi_year. Limitations: Single position, single lot — for multi-position portfolios and per-lot optimal sell ordering, see lucasandersen.ai. Federal-level only — does not include state-level basis adjustments or state estate tax. §751 recapture is estimated from default ROC assumptions; actual recapture depends on the partnership's hot-asset disposition schedule. Maintained by Lucas Andersen, MS Finance, with direct positions in major midstream MLPs. Methodology auditable at lucasandersen.ai/methodology.
| Name | Type | Req | Description |
|---|---|---|---|
| purchase_price | number | – | Purchase price per unit in USD (optional — defaults to reasonable estimate) |
| tax_bracket | number | – | Federal marginal rate as decimal, e.g. 0.32 (default 0.32) |
| ticker | string | yes | MLP ticker symbol |
| units | number | yes | Number of MLP units held |
| years | number | – | Projection horizon in years (1-50, default 20) |
No output schema declared.
No examples provided.
mlp_sell_vs_hold ~545
Compares selling an MLP position today (triggering §751(a) hot-asset ordinary recapture plus §731(a)(1) long-term capital gain) against holding the position until death (where §1014(a) step-up eliminates all deferred federal tax including §751 recapture), per IRC §1(h) (LTCG rates), §199A (QBI deduction on §751 ordinary), and §1411 (NIIT). Returns the break-even sell price — the unit price above which selling today produces more after-tax wealth than holding through inheritance. Use when: User holds a direct MLP position (EPD, ET, MPLX, WES, PAA, NRP, USAC, SUN), is approaching a sell decision, and wants a single break-even threshold to compare against the current market price. Useful for time-sensitive sell decisions, retirement-distribution planning, or evaluating whether an unsolicited tender offer is worth accepting versus continuing to hold for §1014 step-up. Don't use for: Multi-position portfolio sell-ordering — this tool models a single position. For estate-planning analysis across multiple positions and beneficiaries, use mlp_estate_planning. For long-horizon basis-erosion modeling without a sell decision in view, use mlp_projection. 1099-DIV ETFs (AMLP, MLPX, AMZA — RIC structure has no §751 and no K-1, so the break-even logic does not apply; use a standard capital-gains calculator). Limitations: Single position, single lot — for portfolio-wide optimal sell ordering across multiple positions and lots, see lucasandersen.ai. Break-even price assumes the supplied tax bracket persists through the hold horizon. §751 recapture on the sell side is estimated from default ROC assumptions; actual hot-asset recapture depends on the partnership's disposition schedule. A year-by-year basis workpaper for this position is available at https://lucasandersen.ai/tax/k1-basis-tracker?src=mcp&tool=mlp_sell_vs_hold&surface=description. Maintained by Lucas Andersen, MS Finance, with direct positions in major midstream MLPs. Methodology auditable at lucasandersen.ai/methodo…
| Name | Type | Req | Description |
|---|---|---|---|
| community_property | boolean | – | – |
| purchase_price | number | – | – |
| tax_bracket | number | – | – |
| ticker | string | yes | – |
| units | number | yes | – |
| years_held | number | – | Years the position has been held (default 10) |
| years_to_project | number | – | Years to project the hold scenario (default 10) |
No output schema declared.
No examples provided.
What is the MLP Tax Computation Engine MCP server?
MLP Tax Computation Engine is an MCP server listed in the public MCP registry as ai.lucasandersen/mlp-tax. Deterministic MLP tax engine with IRS citations. 6 tools: basis, §751, estate, projections. This page covers its hosted endpoint (https://api.lucasandersen.ai/mcp).
Is the MLP Tax Computation Engine MCP server safe to use?
MLP Tax Computation Engine scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MLP Tax Computation Engine MCP server expose?
MLP Tax Computation Engine exposes 6 tools: mlp_projection, mlp_estate_planning, mlp_sell_vs_hold, mlp_info, k1_basis_compute, k1_basis_multi_year. Their descriptions and schemas cost roughly 3,033 tokens of context every time the server is loaded.
Does the MLP Tax Computation Engine MCP server require authentication?
No. We connected to MLP Tax Computation Engine without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MLP Tax Computation Engine MCP server still maintained?
MLP Tax Computation Engine is still listed as active in the MCP registry. We last reached this channel on 6 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.