Here you go:
https://ponder.cat/wp/wp-sources.zip
It's in python, suitable for sticking directly into the bot if the bot is in python. There are docs. It's a first cut. How did you envision this working? I can make a real API, if for some reason that makes things easier, but it's not immediately obvious how it would get integrated into things.
Running it on the last 50 articles posted to /c/politics, we see:
It's more complex to use this than MBFC, because there's a lot more depth to the rankings, and sometimes human judgement is needed to assign scores. There's a category "needinfo," meaning it's necessary to know what topic is being discussed or when an article was written, because of an ownership change or similar factor. I've applied that judgement above. That, to me, is a good thing. It means the bot is grounded in something, and not just blithely spitting out arbitrary scores without bothering to ground them in any reality.
In practice, I think it would be realistic to assign a single reliability ranking to most of the "needinfo" sources. You can manually edit the .json data to do so. Almost all of the posts are going to fit into one of Wikipedia's categorizations or another. Newsweek is unreliable, The Guardian is reliable, and so on.
I think most of the mixed-consensus sources can be used without a second thought. Mostly, the questions about them boil down to open partisanship of the source, which for a political community is perfectly fine as long as they're trustable factually.
If you want me to boil this down further, so that it gives a single "yes" or "no" score to each source, I can do that and probably keep almost all of the accuracy of the rankings, now that I've looked at it for a little while.
When you talk about "adding" this to the bot, are you proposing to still have MBFC be the main source, with this as a footnote? A lot of the criticism of the bot is on the grounds that MBFC is a very bad source for judging reliability, so I would question the idea of keeping it on as the primary source.